Deluge shutdown time slow 1.3.6+1.3.7
Posted: Fri Sep 19, 2014 12:28 pm
Hi,
Win 7 x64 both 1.3.6 and 1.3.7 using deluged.exe and thin client.
I have about 20 torrents, most of them just sitting there idle waiting for someone to get them off me (to seed properly for private tracker rules).
A few of them active downloads...
The problem is shutdown. Don't want an unclean shutdown which forces a recheck!
I have followed the instructions using NSSM as a service, but the shutdown is odd... takes a long time even when no activity has happened during a session!
When sent a signal to shut down:
What I see in task manager, is the handles drop to 0, and memory slowly drops down, until up to 10 minutes it shuts down. The thin client can't connect (of course- but just to show that deluge is in shut down mode).
In resource manager, disk activity is nothing... so deluge is not writing files or using any CPU. I have also confirmed with process hacker program that disk activity is almost nothing.
So, what is deluge doing- and why would it take so long to be shutting down, even after just running a few minutes of little to no activity? If it is not cpu limited or disk limited... something is making it wait wait wait. I've tried cache sizes that are small and big, no change. Even played around with the ltconfig plugin...
Win 7 x64 both 1.3.6 and 1.3.7 using deluged.exe and thin client.
I have about 20 torrents, most of them just sitting there idle waiting for someone to get them off me (to seed properly for private tracker rules).
A few of them active downloads...
The problem is shutdown. Don't want an unclean shutdown which forces a recheck!
I have followed the instructions using NSSM as a service, but the shutdown is odd... takes a long time even when no activity has happened during a session!
When sent a signal to shut down:
What I see in task manager, is the handles drop to 0, and memory slowly drops down, until up to 10 minutes it shuts down. The thin client can't connect (of course- but just to show that deluge is in shut down mode).
In resource manager, disk activity is nothing... so deluge is not writing files or using any CPU. I have also confirmed with process hacker program that disk activity is almost nothing.
So, what is deluge doing- and why would it take so long to be shutting down, even after just running a few minutes of little to no activity? If it is not cpu limited or disk limited... something is making it wait wait wait. I've tried cache sizes that are small and big, no change. Even played around with the ltconfig plugin...
