If by "does not close on exit" you mean it takes a looong time for the process to exit then it's a known issue and it should get better when qbt adopts a newer libtorrent version.

Other than that did you uncheck Options->Behavior->Close qBittorrent to notification area? I fell for it several times on clean qbt installations...

@thalieht commented on GitHub (Jan 9, 2017): If by "does not close on exit" you mean it takes a looong time for the process to exit then it's a known issue and it should get better when qbt adopts a newer libtorrent version. Other than that did you uncheck Options->Behavior->Close qBittorrent to notification area? I fell for it several times on clean qbt installations...

deekerman commented

2026-02-21 17:40:18 -05:00

Author

Owner

@Bogged commented on GitHub (Jan 9, 2017):

hmmm. I'm new to this forum platform (no quoting system?)

"If by "does not close on exit" you mean it takes a looong time for the process to exit then it's a known issue and it should get better when qbt adopts a newer libtorrent version."

Ah that's a good one. Then "does not close on exit" is a false statement if it takes a lifetime to close?
After few tests it looks like sometimes it takes a loooooooooooooong and some other times it's so long that I don't have the patience to wait and kill the process myself.

"Other than that did you uncheck Options->Behavior->Close qBittorrent to notification area? I fell for it several times on clean qbt installations.."

Nah I want to see the qbt icon at all times when it's running. Which brings me to a second issue/comment. Should I start another issue or put it in a recommendation. Since it's a known issue that QBT process closes when it feels like it. Is it possible to force the icon to stay in the notification bar as long as the process is running (after a close request sent by the user)?

@Bogged commented on GitHub (Jan 9, 2017): hmmm. I'm new to this forum platform (no quoting system?) "If by "does not close on exit" you mean it takes a looong time for the process to exit then it's a known issue and it should get better when qbt adopts a newer libtorrent version." Ah that's a good one. Then "does not close on exit" is a false statement if it takes a lifetime to close? After few tests it looks like sometimes it takes a loooooooooooooong and some other times it's so long that I don't have the patience to wait and kill the process myself. "Other than that did you uncheck Options->Behavior->Close qBittorrent to notification area? I fell for it several times on clean qbt installations.." Nah I want to see the qbt icon at all times when it's running. Which brings me to a second issue/comment. Should I start another issue or put it in a recommendation. Since it's a known issue that QBT process closes when it feels like it. Is it possible to force the icon to stay in the notification bar as long as the process is running (after a close request sent by the user)?

deekerman commented

2026-02-21 17:40:18 -05:00

Author

Owner

@zeule commented on GitHub (Jan 9, 2017):

@Bogged, there is a link below the editor window (entitled "Styling with Markdown is supported") where you can lookup possible markup elements.

As per the issue itself, I doubt anything except a stacktrace of the program when it is "halted" could be useful. So, if you can reproduce the issue, running qBt under a debugger, please share stacktraces from all threads.

@zeule commented on GitHub (Jan 9, 2017): @Bogged, there is a link below the editor window (entitled "Styling with Markdown is supported") where you can lookup possible markup elements. As per the issue itself, I doubt anything except a stacktrace of the program when it is "halted" could be useful. So, if you can reproduce the issue, running qBt under a debugger, please share stacktraces from all threads.

deekerman commented

2026-02-21 17:40:18 -05:00

Author

Owner

@Bogged commented on GitHub (Jan 9, 2017):

"As per the issue itself, I doubt anything except a stacktrace of the program when it is "halted" could be useful. So, if you can reproduce the issue, running qBt under a debugger, please share stacktraces from all threads."

Since it's a known problem, I'm just going to wait until it gets resovled. Meanwhile I will manually kill the process after quitting exiting qbt.

Anyone know what is the last release without this issue?

@Bogged commented on GitHub (Jan 9, 2017): "As per the issue itself, I doubt anything except a stacktrace of the program when it is "halted" could be useful. So, if you can reproduce the issue, running qBt under a debugger, please share stacktraces from all threads." Since it's a known problem, I'm just going to wait until it gets resovled. Meanwhile I will manually kill the process after quitting exiting qbt. Anyone know what is the last release without this issue?

deekerman commented

2026-02-21 17:40:18 -05:00

Author

Owner

@zeule commented on GitHub (Jan 9, 2017):

I had such a problem, but it was caused by boost::asio and disappeared with boost version 1.62.0.

@zeule commented on GitHub (Jan 9, 2017): I had such a problem, but it was caused by boost::asio and disappeared with boost version 1.62.0.

deekerman commented

2026-02-21 17:40:18 -05:00

Author

Owner

@dzmat commented on GitHub (Jan 11, 2017):

windows version 3.3.10 already is linked against boost 1.62.0 version, so it is not a case.

@dzmat commented on GitHub (Jan 11, 2017): windows version 3.3.10 already is linked against boost 1.62.0 version, so it is not a case.

deekerman commented

2026-02-21 17:40:18 -05:00

Author

Owner

@dzmat commented on GitHub (Jan 11, 2017):

@Bogged does qbittorrent process remain in process list if you close it by using menu entry File->Quit, not the cross button in window handle?

@dzmat commented on GitHub (Jan 11, 2017): @Bogged does qbittorrent process remain in process list if you close it by using menu entry File->Quit, not the cross button in window handle?

deekerman commented

2026-02-21 17:40:18 -05:00

Author

Owner

@zeule commented on GitHub (Jan 11, 2017):

@dzmat, beg your pardon, 1.63.0

@zeule commented on GitHub (Jan 11, 2017): @dzmat, beg your pardon, 1.63.0

deekerman commented

2026-02-21 17:40:18 -05:00

Author

Owner

@Bogged commented on GitHub (Jan 11, 2017):

"@Bogged does qbittorrent process remain in process list if you close it by using menu entry File->Quit, not the cross button in window handle?"

I think I tried both - But cross handle is suppose to reduce in the tray no?

My experience is mainly with file/quit and/or with the quit enabled after all downloads completed.

@Bogged commented on GitHub (Jan 11, 2017): "@Bogged does qbittorrent process remain in process list if you close it by using menu entry File->Quit, not the cross button in window handle?" I think I tried both - But cross handle is suppose to reduce in the tray no? My experience is mainly with file/quit and/or with the quit enabled after all downloads completed.

deekerman commented

2026-02-21 17:40:18 -05:00

Author

Owner

@thisisnotmyrealname commented on GitHub (Jan 11, 2017):

file -> quit takes an eternity to quit on 3.3.10 x64, windows 10, ~400 torrents.

@thisisnotmyrealname commented on GitHub (Jan 11, 2017): file -> quit takes an eternity to quit on 3.3.10 x64, windows 10, ~400 torrents.

deekerman commented

2026-02-21 17:40:18 -05:00

Author

Owner

@zeule commented on GitHub (Jan 11, 2017):