2.2.1 Crash on exit with a SIGSEGV (UPnP plugin)

Bug #132014 reported by Ibrahim
2
Affects Status Importance Assigned to Milestone
ktorrent (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi,

I read a few bug reports about Ktorrent crashes, but I think this is a new one.

Every time I shutdown Ktorrent I get a nasty Crash Handler Screen (the crash is nasty, not the screen ;) ).
As you can see from the Back Trace, it crashes when trying to unload the plugins. So I did some tests (a dozen shutdowns and ten crashes ...) and found out that the UPnP plugin is the culprit. It does not crash when I unload it in the Plugins list inside Ktorrent. Only when closing down Ktorrent.

I'm using the back ports so Ktorrent is version 2.2.1-0ubuntu1~feisty1. I'm under Kubuntu Feisty. Any more information you might need ? Oh, one more thing, it didn't crash with the previous version (2.2.0).

Here is the back trace :

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47991739505792 (LWP 15101)]
(no debugging symbols found)
...
(no debugging symbols found)
[KCrash handler]
#5 0x0000000000000000 in ?? ()
#6 0x00002ba5eb6d4c82 in kt::PluginManager::unloadAll ()
   from /usr/lib/libktorrent-2.2.1.so
#7 0x0000000000430fdf in ?? ()
#8 0x00002ba5ec64150d in KMainWindow::shuttingDown ()
   from /usr/lib/libkdeui.so.4
#9 0x00002ba5ec75da4d in KMainWindow::qt_invoke ()
   from /usr/lib/libkdeui.so.4
#10 0x00002ba5ebc6e95e in KParts::MainWindow::qt_invoke ()
   from /usr/lib/libkparts.so.2
#11 0x000000000047bc0d in ?? ()
#12 0x0000000000433c00 in ?? ()
#13 0x00002ba5ee330ce2 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#14 0x00002ba5ee33187c in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#15 0x00002ba5ecf9ada2 in KApplication::qt_emit ()
   from /usr/lib/libkdecore.so.4
#16 0x00002ba5ecf9adc9 in KUniqueApplication::qt_emit ()
   from /usr/lib/libkdecore.so.4
#17 0x0000000000436789 in ?? ()
#18 0x00002ba5ee330de6 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#19 0x00002ba5ee33187c in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#20 0x00002ba5ee698501 in QApplication::aboutToQuit ()
   from /usr/lib/libqt-mt.so.3
#21 0x00002ba5ee2e57fd in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#22 0x00002ba5ee2e5513 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#23 0x00002ba5ee2cdc9c in QApplication::exec () from /usr/lib/libqt-mt.so.3
#24 0x000000000044c355 in ?? ()
#25 0x00002ba5f1df68e4 in __libc_start_main () from /lib/libc.so.6
#26 0x000000000042b939 in ?? ()
#27 0x00007fffbf6770c8 in ?? ()
#28 0x0000000000000000 in ?? ()

Revision history for this message
John Dong (jdong) wrote :

Hi,

Thanks for the bug report. This is a duplicate of bug #130300, which was fixed yesterday in Gutsy. I'd like to wait for a bit confirmation that it is fixed in Gutsy, then I will backport it to all Ubuntu releases.

Revision history for this message
Ibrahim (ib80) wrote :

Thank you for responding so fast.

I did see that bug, but I guess it was a bit too late.

Sorry for the bother.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.