-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Caught signal: SIGABRT on closing qbt #11399
Comments
This stack dump looks messed up to me, all those |
HandleTorrenResumeDataReady() should probably handle errors. Or possibly a a function ahead of it on the call stack. But the destructor should not leak exceptions. |
@arvidn Is this still relevant? I'd like to close this, but let me know if there is still any relevant information that you need from here or something that you'd like to investigate further. |
If you have any issues with the latest version, on a supported OS, please open a new issue report. Thank you for your contributions. |
qBittorrent version: v4.1.8 (32-bit)
Libtorrent version: 1.1.13.0
Qt version: 5.6.3
Boost version: 1.71.0
OS version: Windows XP 5.1.2600 i386
Caught signal: SIGABRT
Extra info(if any)
This crash has occurred shortly after closing. Reason for closing was no d/l at all (seeding was OK), tried to Pause/Resume/[F]Resume. Perhaps related to #11375?
qbt used 1.1GB of private memory, which is high, but not the highest observed on my machine.
qbt was still happily writing out .fastresume files while the crash window was open...
The text was updated successfully, but these errors were encountered: