| Summary: | Crash when magnet removed from list | ||
|---|---|---|---|
| Product: | [Applications] ktorrent | Reporter: | Darin McBride <Tanktalus> |
| Component: | general | Assignee: | Joris Guisson <joris.guisson> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | matej |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Darin McBride
2018-07-21 13:34:17 UTC
Created attachment 124054 [details]
New crash information added by DrKonqi
ktorrent (5.1.2) using Qt 5.12.5
- What I was doing when the application crashed:
Opened magnet link from browser, magnet was being dowloaded, crash right when the magnet was successfully downloaded apparently.
-- Backtrace (Reduced):
#7 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#8 0x00007f5ea8a868c5 in __GI_abort () at abort.c:79
#9 0x00007f5ead31cbd8 in bt::QtMessageOutput (type=<optimized out>, msg=...) at /var/tmp/portage/net-libs/libktorrent-2.1.1/work/libktorrent-2.1.1/src/util/log.cpp:312
#10 0x00007f5ea94b110e in qt_message_print (msgType=QtFatalMsg, context=..., message=...) at global/qlogging.cpp:1836
[...]
#12 0x00007f5ea947136e in QMessageLogger::fatal (this=this@entry=0x7ffc58afaae0, msg=msg@entry=0x7f5ea973d0a8 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:885
Created attachment 125070 [details]
New crash information added by DrKonqi
ktorrent (5.1.2) using Qt 5.13.2
- What I was doing when the application crashed:
Clicked on a magnet link, the magnet quickly downloaded, then KTorrent crashes, probably when removing the magnet from a list of magnets to download.
To reproduce, one can just call ktorrent 'magnet:?xt=urn:btih:712922130bb7d83696a18a139454ce0a74455134&dn=Apocalypse-The+Second+World+War+-+Season+1&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Fopen.demonii.com%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Fexodus.desync.com%3A6969'
My Qt is compiled with debug assertions enabled. (that seems necessary to reproduce the bug).
-- Backtrace (Reduced):
#7 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#8 0x00007f20c264b535 in __GI_abort () at abort.c:79
#9 0x00007f20c4ac9bd8 in bt::QtMessageOutput (type=<optimized out>, msg=...) at /var/tmp/portage/net-libs/libktorrent-2.1.1/work/libktorrent-2.1.1/src/util/log.cpp:312
#10 0x00007f20c2ca0c68 in qt_message_print (msgType=QtFatalMsg, context=..., message=...) at global/qlogging.cpp:1836
[...]
#12 0x00007f20c2c56782 in QMessageLogger::fatal (this=this@entry=0x7fff750aed90, msg=msg@entry=0x7f20c2f3df68 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:885
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |