Not Responding

Windows specific questions, problems.
Post Reply
MartynK

Not Responding

Post by MartynK »

I have QB running on a Windows 11 VM with 4 cores and 8gb memory.

The software runs great, downloads and does all I ask expect randomly I get "Not Responding" when I login to the VM and all I can do is kill QB and restart it. Its totally random as to how long between me using the VM and it happening, could be hours or even days.

I have tried different versions, v4.3.5, v4.3.9, v4.4.0 and I have the same issue with all.

Generally I am running around 30~40 torrents, of which I limit the setup to 10 down and 10 up active at any time.

Anyone got any ideas ?
evr

Re: Not Responding

Post by evr »

I'm having a similar problem..
Tried to open QT today and all my search plugins are gone..
Attempted to update/reinstall them keep getting a "not responding" message..
User avatar
Peter
Administrator
Administrator
Posts: 3049
Joined: Wed Jul 07, 2010 6:14 pm

Re: Not Responding

Post by Peter »

What kind of virtual machine are you using? Like what software?
Also, stick to 4.3.9 until the 4.4.x issues are fixed.
MartynK

Re: Not Responding

Post by MartynK »

Hi,
Its running Windows 11 Pro on VM workstation Pro.

The underlying box has Windows 11 Pro running.
Its an 16 Core i7 with 64gb memory.

I will try v4.3.9 now.

Thanks
MartynK

Re: Not Responding

Post by MartynK »

So I went back to v4.3.9 as advised, but at some point this morning I see that it stopped responding again.

The only thing that I can see that has happened is that Sonarr has moved some of the torrents from their original download locations to my library and not removed the torrent from QB, so its still showing as available.

When I restarted QB, all the torrents that had had files moved then showed a status of "files missing" in red text.

Could this be a clue ?
MartynK

Re: Not Responding

Post by MartynK »

I am still having issues with this, I downgraded to v4.3.5 as it does seem to work a little more between crashing.

This really does seem to be something to do with running on a VM and the VM being locked as I logout, I just cannot fathom what.
Post Reply