Bug 399411 - crashes on close
Summary: crashes on close
Status: RESOLVED FIXED
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-10-05 15:43 UTC by smellymoo
Modified: 2020-12-02 10:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description smellymoo 2018-10-05 15:43:27 UTC
Application: ktorrent (5.1.0)

Qt Version: 5.11.1
Frameworks Version: 5.48.0
Operating System: Linux 4.18.10-200.fc28.x86_64 x86_64
Distribution: "Fedora release 28 (Twenty Eight)"

-- Information about the crash:
- What I was doing when the application crashed:
close the app

this happens about 1/3 of the time. has happened since atleast fedora 28 being released.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f88db598940 (LWP 12463))]

Thread 4 (Thread 0x7f88ad7ac700 (LWP 12483)):
#0  0x00007f88e7dd8730 in nanosleep () at /lib64/libc.so.6
#1  0x00007f88e8cb5b15 in qt_nanosleep(timespec) () at /lib64/libQt5Core.so.5
#2  0x00007f88ee8c99bd in net::UploadThread::update() () at /lib64/libKF5Torrent.so.6
#3  0x00007f88ee8c9fa9 in net::NetworkThread::run() () at /lib64/libKF5Torrent.so.6
#4  0x00007f88e8ad5b4b in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#5  0x00007f88e3995594 in start_thread () at /lib64/libpthread.so.0
#6  0x00007f88e7e0be6f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f88adfad700 (LWP 12482)):
#0  0x00007f88e7e013e9 in poll () at /lib64/libc.so.6
#1  0x00007f88ee8ccd2a in net::Poll::poll(int) () at /lib64/libKF5Torrent.so.6
#2  0x00007f88ee8c9cca in net::DownloadThread::waitForSocketReady() () at /lib64/libKF5Torrent.so.6
#3  0x00007f88ee8c9d5a in net::DownloadThread::update() () at /lib64/libKF5Torrent.so.6
#4  0x00007f88ee8c9fa9 in net::NetworkThread::run() () at /lib64/libKF5Torrent.so.6
#5  0x00007f88e8ad5b4b in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#6  0x00007f88e3995594 in start_thread () at /lib64/libpthread.so.0
#7  0x00007f88e7e0be6f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f88c6ec2700 (LWP 12467)):
#0  0x00007f88e7e013e9 in poll () at /lib64/libc.so.6
#1  0x00007f88dfac2bc6 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#2  0x00007f88dfac2cf0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#3  0x00007f88e8cb62ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#4  0x00007f88e8c64b7b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#5  0x00007f88e8acc6b6 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x00007f88e9a867b9 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5
#7  0x00007f88e8ad5b4b in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#8  0x00007f88e3995594 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f88e7e0be6f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f88db598940 (LWP 12463)):
[KCrash Handler]
#6  0x00007f88ee8ee7db in bt::AccessManager::~AccessManager() () at /lib64/libKF5Torrent.so.6
#7  0x00007f88e7d4b5ec in __run_exit_handlers () at /lib64/libc.so.6
#8  0x00007f88e7d4b71c in  () at /lib64/libc.so.6
#9  0x00007f88e7d35122 in __libc_start_main () at /lib64/libc.so.6
#10 0x000055ccdbc7643a in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 369352.

Reported using DrKonqi
Comment 1 Patrick Silva 2018-10-05 23:29:23 UTC

*** This bug has been marked as a duplicate of bug 383127 ***
Comment 2 Christoph Feck 2018-10-06 08:56:17 UTC
Backtrace is not related; deduplicate.
Comment 3 Justin Zobel 2020-12-02 05:26:54 UTC
Thank you for the report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thank you.
Comment 4 smellymoo 2020-12-02 09:57:16 UTC
I left Ktorrent, had other issues (bad upnp), so can't help.
Comment 5 Justin Zobel 2020-12-02 10:00:41 UTC
Setting to status to resolved as user unable to reproduce.