abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: qbittorrent component: qbittorrent executable: /usr/bin/qbittorrent kernel: 2.6.31.5-127.fc12.x86_64 package: qbittorrent-2.2.5-1.fc12 rating: 3 reason: Process /usr/bin/qbittorrent was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1.not sure 2. 3.
Created attachment 406169 [details] File: backtrace
Reassigned to qt
*** Bug 583196 has been marked as a duplicate of this bug. ***
This is an issue which needs to be addressed by the upstream developers. Please file a report at http://bugs.kde.org once that is done please add the upstream bug information to this report. We will monitor the upstream report for a resolution. Thanks
*** Bug 592656 has been marked as a duplicate of this bug. ***
*** Bug 592552 has been marked as a duplicate of this bug. ***
*** Bug 583264 has been marked as a duplicate of this bug. ***
*** Bug 591328 has been marked as a duplicate of this bug. ***
*** Bug 595149 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > This is an issue which needs to be addressed by the upstream developers. > Please file a report at http://bugs.kde.org once that is done please add the > upstream bug information to this report. We will monitor the upstream report > for a resolution. > > Thanks Why http://bugs.kde.org ?
I think bko was just a paste-o , qt upstream is nokia, whose tracker is at http://bugreports.qt.nokia.com/
*** Bug 598669 has been marked as a duplicate of this bug. ***
(In reply to comment #9) > *** Bug 595149 has been marked as a duplicate of this bug. *** Bug 595149 was filed against the F13 qt package
*** Bug 600833 has been marked as a duplicate of this bug. ***
*** Bug 603479 has been marked as a duplicate of this bug. ***
*** Bug 604506 has been marked as a duplicate of this bug. ***
*** Bug 614223 has been marked as a duplicate of this bug. ***
*** Bug 610995 has been marked as a duplicate of this bug. ***
*** Bug 610997 has been marked as a duplicate of this bug. ***
*** Bug 610994 has been marked as a duplicate of this bug. ***
*** Bug 616421 has been marked as a duplicate of this bug. ***
So all these bugs have in common that qbittorrent crashes while destroying the QApplication, usually in QMultiInputContext. It is the only app we're getting these reports for, and qbittorrent's source code has this to say: qDebug("Deleting app..."); #ifndef Q_WS_WIN // XXX: Why does it crash on Windows in QWindowsVistaStyle destructor!? delete app; #endif so it looks like they're already noticing crashes during QApplication destruction on other platforms. I suspect some memory corruption inside qbittorrent. Please try running qbittorrent in Valgrind to see if that tells us the true cause of the bug. At this stage, I really don't think it's a Qt bug, sorry. The crashes should also be reported to qbittorrent upstream on SourceForge.
Can this be reproduced with a recent qBittorrent version (v2.2.10)? There used to be an issue where the QApplication was instantiated too late in the main() and this was fixed in v2.2.9 or v2.2.10. Regarding the piece of code provided by Kevin Kofler. This is outdated and no longer existing in recent qBittorrent. This was added temporarily until we finished Windows porting. Just so you know, the crash when deleting the QApplication was due to linking problems on Windows and not to a bug in qBittorrent.
(In reply to comment #23) > Can this be reproduced with a recent qBittorrent version (v2.2.10)? > > There used to be an issue where the QApplication was instantiated too late in > the main() and this was fixed in v2.2.9 or v2.2.10. > Yes it was still present in 2.2.9 https://bugzilla.redhat.com/show_bug.cgi?id=610995
Any Fedora-specific patches/changes? I'm asking because I'm not getting similar reports from other distributions users but there seems to be a lot of duplicates reports here... Anyway, I will follow Kevin Kofler's hint and use Valgrind to debug possible memory problems. I hope we can figure out the reason soon.
Well, Fedora is using an automated crash intercepting and reporting tool which has been used to file all those reports: https://fedoraproject.org/wiki/Features/ABRT It's quite likely that crashes on exit in a GUI app (i.e. an app normally run from a menu, not a terminal) otherwise go entirely unnoticed.
This is a known bug in Qt 4.6: http://bugreports.qt.nokia.com/browse/QTBUG-7105 Here is the patch I propose: http://launchpadlibrarian.net/52219219/force-inputcontext.patch I have implemented in the patch the workaround proposed in the Qt bug report: *** Another workaround would be to make sure the input context is created BEFORE the application destructor is called, e.g. for KDE, this could be done inside KApplication by just calling (void) QApplication::inputContext() for GUI applications. *** In my case, I create the input context just after creating the QApplication.
By the way, my patch is a workaround for qBittorrent, not a patch for Qt.
We could also apply a Qt patch if there's a known one, but I guess that for now the qbittorrent workaround is the easiest fix. What I wonder is why qbittorrent is the only app we get bug reports about.
Here is the known Qt patch: http://qt.gitorious.org/qt/staging/commit/f72165460d27860cabd51691f4d935fd74b50f80
By the way, I have Qt 4.6.2 and it already contains the fix. Only Qt 4.6.0 (and maybe Qt 4.6.1?) seem to be affected
Then either it's not that bug or the fix does not work. We have 4.6.3 (pushed on July 13), and before that we had 4.6.2 (pushed to F12 on February 24 along with KDE 4.4.0, F13 shipped with it).
I believe this is fixed in v2.2.11 (both the crash on exit and the library shipping). It seems it was caused by an error on my code after all, mea culpa. My memory clean up code was a little too extreme and it was sometimes destructing objects belonging to the QApplication instance. I hope that all is in order now. Sorry not fixing this earlier but it was tricky to debug.
*** Bug 619352 has been marked as a duplicate of this bug. ***
*** Bug 618604 has been marked as a duplicate of this bug. ***
*** Bug 618127 has been marked as a duplicate of this bug. ***
*** Bug 618051 has been marked as a duplicate of this bug. ***
*** Bug 617902 has been marked as a duplicate of this bug. ***
*** Bug 617791 has been marked as a duplicate of this bug. ***
*** Bug 616542 has been marked as a duplicate of this bug. ***
*** Bug 615784 has been marked as a duplicate of this bug. ***
*** Bug 617681 has been marked as a duplicate of this bug. ***
*** Bug 619852 has been marked as a duplicate of this bug. ***
Package: qbittorrent-1:2.2.8-2.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Starting Qbittorrent 2. Closing Qbittorrent 3.
Leigh > I see that John de Loos still has v2.2.8. I am confident that this bug was fixed in v2.2.11. Did you cherry pick the patch for your v2.2.8 package or not?
Package: qbittorrent-1:2.2.8-2.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Closing qBittorrent 2. 3.
(In reply to comment #46) > Leigh > I see that John de Loos still has v2.2.8. I am confident that this bug > was fixed in v2.2.11. Did you cherry pick the patch for your v2.2.8 package or > not? The reports have stopped so I will close this Br.