Notes |
|
|
I'm not sure about Windows, but on OS X it was here forever. After pressing the Close button, the app is still clearly running, sitting here in Dock, for quite a long time, up to half minute. |
|
|
(0009903)
|
Blzut3
|
2014-07-08 10:38
|
|
I know program termination is sometimes held up by waiting for the refresher thread to close, but I believe that should take a minute or two tops. |
|
|
|
"I know program termination is sometimes held up by waiting for the refresher thread to close, but I believe that should take a minute or two tops."
Well it doesn't to me. They never close unless I close them myself.
It doesn't stay open all times either, but most of them.
|
|
|
(0009921)
|
Zalewa
|
2014-07-09 17:38
|
|
I've actually noticed it myself, but I'm not sure what exactly causes this or how can this be reproduced. |
|
|
(0011502)
|
Zalewa
|
2015-01-22 17:17
|
|
Does this still occur when you update to the newest beta build? If not, then I'm going to close this with "cannot reproduce" resolution. |
|
|
(0011548)
|
Zalewa
|
2015-01-28 16:26
|
|
|
|
|
|
|
(0011555)
|
Zalewa
|
2015-01-28 21:42
|
|
Are you sure these aren't actually valid instances that live in the system tray? The 'X' button in top-right corner may not quit the program depending on the configuration. Selecting "File -> Quit" should do it definitely. |
|
|
(0011556)
|
Visual Vincent
|
2015-01-28 23:48
(edited on: 2015-01-28 23:55) |
|
Why would it run in the system tray? Have you made it able to do that? Because if you haven't, it's not possible for the application to do so. :)
And yes, it still happens when I use "File > Quit"
|
|
|
(0011558)
|
Zalewa
|
2015-01-29 06:02
|
|
Quote from "Visual Vincent"
Why would it run in the system tray? Have you made it able to do that? Because if you haven't, it's not possible for the application to do so. :)
Yes, we've made it able to do that. User can toggle it in "Appearance" page in the config box.
Is this reproducible 100% of times? Do you do anything specific before closing the program or do you just start it and then immediately close it? |
|
|
(0011563)
|
Zalewa
|
2015-01-29 16:24
|
|
I have deployed an update to the "beta" auto-update channel with a change that can possibly help with the issue. Can you check now? |
|
|
(0011566)
|
Zalewa
|
2015-01-29 22:41
(edited on: 2015-01-29 22:42) |
|
I've nailed it down and can reproduce it reliably. It occurs when you have "IP to hostname resolving" enabled and close the program before it resolves all IPs. It also happens on Windows only. See the "where it gets stuck.png" picture I attached.
You can fix the problem by disabling "Lookup server hosts" in "Appearance" config box.
We're currently using Qt 4.8.5 on Windows. I'll try updating to Qt 4.8.6 and see if it fixes the problem. If not, we might be forced to remove the feature completely in Windows builds as it breaks the program badly.
|
|
|
(0011571)
|
Zalewa
|
2015-01-30 22:04
|
|
|