Page 1 of 1
Slow shutting down [win 10] 3.2.0RC1
Posted: February 5th, 2021, 2:44 pm
by noob
If I download something and then delete the download without pausing clicking on the delete icon and then if I want to restart or shut it down it takes too much time 15/20 + more seconds and sometimes download shut down so I have to manually force it shut down from Task manager.
Re: Slow shutting down [win 10] 3.2.0RC1
Posted: February 5th, 2021, 3:14 pm
by noob
Ok not just 15/20seconds its not shutting down now. 1 minutes have passed it is not shutting down.
Re: Slow shutting down [win 10] 3.2.0RC1
Posted: February 5th, 2021, 3:24 pm
by noob
3.1.1 doesnt have these problems.
Re: Slow shutting down [win 10] 3.2.0RC1
Posted: February 5th, 2021, 3:33 pm
by safihre
Could you enable Debug logging in the Status and Interface settings window and then try again, after that send me the logs (click Show Logging in the Status window) at
[email protected]?
Re: Slow shutting down [win 10] 3.2.0RC1
Posted: February 5th, 2021, 6:26 pm
by noob
There is another thing I am noticing between 3.1.1 vs 3.2.0RC1
3.1.1 aggressively wants to connect to provider servers. and it retries quickly if anything goes wrong vs 3.2.0 is slower and takes much time. same thing for pause resume too.
Im monitoring the connections with third-party apps. Im back to 3.1.1 and its UI feels snappy and smoother too.
I will reinstall the 3.2.0 RC1 and will send you Debug log.
Re: Slow shutting down [win 10] 3.2.0RC1
Posted: February 6th, 2021, 1:39 am
by safihre
There have been some changes to ignore servers if they haven't participated in a while, maybe those are interfering with expected behavior.
Re: Slow shutting down [win 10] 3.2.0RC1
Posted: February 6th, 2021, 7:02 am
by Puzzled
I don't know about the slow shutdown, but the problem with connecting could be because the simplified article search delay will also make it skip the busy_threads checks. It should probably only skip the server checks if there are no busy_threads. I suggest moving the next_article_search check below the server.restart block.
Edit: The next_article_search delay should be skipped completely if there are busy_threads. Resetting the connections will reset the try_list, so the article will have to be fetched again.