Bug 458058 - ktorrent crashes when a magnet "data download" is done and the actual torrent starts
Summary: ktorrent crashes when a magnet "data download" is done and the actual torrent...
Status: RESOLVED DUPLICATE of bug 458057
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: 22.04.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-08-19 08:29 UTC by Mathias Homann
Modified: 2023-08-15 11:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathias Homann 2022-08-19 08:29:05 UTC
Application: ktorrent (22.04.3)

Qt Version: 5.15.5
Frameworks Version: 5.97.0
Operating System: Linux 5.19.1-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.25.4 [KCrashBackend]

-- Information about the crash:
I'm trying to get some downloads started, but when the "magnet process" is done and the actual torrent starts, ktorrent crashes, and when I restart it, the torrent AND the magnet download are both active, leading to the same crash in a few seconds. repeat ad nauseam.

The crash can be reproduced every time.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fde0c525d7f in kt::MagnetManager::update (this=0x561c9f6819d0) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/libktcore/torrent/magnetmanager.cpp:339
#5  0x0000561c9e903efa in kt::Core::update (this=0x561c9f64ead0) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:900
#6  0x00007fde0a512e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffd5f3cd0e0, r=0x561c9f64ead0, this=0x561c9f680df0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#7  doActivate<false> (sender=0x561c9f64eaf8, signal_index=3, argv=0x7ffd5f3cd0e0) at kernel/qobject.cpp:3886
#8  0x00007fde0a50c22f in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7fde0a7b39a0, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd5f3cd0e0) at kernel/qobject.cpp:3946
#9  0x00007fde0a516aca in QTimer::timeout (this=<optimized out>, _t1=...) at .moc/moc_qtimer.cpp:205
#10 0x00007fde0a50757d in QObject::event (this=0x561c9f64eaf8, e=0x7ffd5f3cd230) at kernel/qobject.cpp:1336
#11 0x00007fde0b1a541e in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x561c9f64eaf8, e=0x7ffd5f3cd230) at kernel/qapplication.cpp:3637
#12 0x00007fde0a4dbfb8 in QCoreApplication::notifyInternal2 (receiver=0x561c9f64eaf8, event=0x7ffd5f3cd230) at kernel/qcoreapplication.cpp:1064
#13 0x00007fde0a532851 in QTimerInfoList::activateTimers (this=0x561c9f3dd3a0) at kernel/qtimerinfo_unix.cpp:643
#14 0x00007fde0a5330e4 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:183
#15 0x00007fde085bfea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#16 0x00007fde085c0258 in ?? () from /lib64/libglib-2.0.so.0
#17 0x00007fde085c02ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#18 0x00007fde0a533456 in QEventDispatcherGlib::processEvents (this=0x561c9f3e8840, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#19 0x00007fde0a4daa2b in QEventLoop::exec (this=this@entry=0x7ffd5f3cd470, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#20 0x00007fde0a4e2b96 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#21 0x0000561c9e8f82b9 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/main.cpp:253
[Inferior 1 (process 7454) detached]

The reporter indicates this bug may be a duplicate of or related to bug 458057, bug 396727.

Reported using DrKonqi
Comment 1 Nicolas Fella 2023-08-15 11:50:43 UTC
*** This bug has been marked as a duplicate of bug 458057 ***