3.3.10.0 for Windows. qbittorrent.exe process does not close on exit #6215

Closed
Bogged opened this Issue Jan 8, 2017 · 12 comments

Projects

None yet

6 participants

@Bogged
Bogged commented Jan 8, 2017

Subject says it all.

@okeatime
Contributor
okeatime commented Jan 9, 2017

Screen shot please?

@thalieht
Contributor
thalieht commented 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...

@Bogged
Bogged commented Jan 9, 2017 edited

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)?

@evsh
Contributor
evsh commented 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.

@Bogged
Bogged commented 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?

@evsh
Contributor
evsh commented Jan 9, 2017

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

@dzmat
Contributor
dzmat commented Jan 11, 2017

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

@dzmat
Contributor
dzmat commented 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?

@evsh
Contributor
evsh commented Jan 11, 2017

@dzmat, beg your pardon, 1.63.0

@Bogged
Bogged commented 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.

@thisisnotmyrealname

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

@evsh
Contributor
evsh commented Jan 11, 2017

Closing as duplicate of #5097.

@evsh evsh closed this Jan 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment