Summary: | Segfault when closing rekonq | ||
---|---|---|---|
Product: | [Unmaintained] rekonq | Reporter: | Cédric Bellegarde <web> |
Component: | general | Assignee: | Andrea Diamantini <adjam7> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | latest git snapshot | ||
Target Milestone: | 0.7 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Cédric Bellegarde
2011-03-02 13:23:31 UTC
Git commit ac57e2cc767405b8eadce5f5d6fd32c8f702a93e by Cedric Bellegarde. Committed on 02/03/2011 at 13:22. Pushed by cedric into branch 'master'. delete bookmarkProvider sooner to prevent segfault BUG:267460 M +2 -0 src/application.cpp http://commits.kde.org/rekonq/ac57e2cc767405b8eadce5f5d6fd32c8f702a93e I cannot understand how this commit can fix this bug. Can you pls explain me? ~Application() call ~QApplication() before calling ~BookmarkProvider() ~BookmarkProvider() call ~QRasterWindowSurface() that seems to need QApplication... http://bugreports.qt.nokia.com/browse/QTBUG-16974 As you can notice, the bug you are referring has been closed as invalid. In fact the right sequence is: ~Application() finishes and starts ~QApplication(). ~QApplication() finishes and starts ~QObject(). ~QObject() destroys before closing ALL its children, so also the BookmarkProvider. Forcing a faster call to ~BookmarkProvider() maybe dangerous, cause of some parts of the Application that can try yet using it. The right fix imho should be "reparent" the GUI objects depending on BookmarkProvider to the MainWindow they belong. Ok, will give a look for a better fix. Many thanks for :) Cedric, can you yet reproduce it? Yes, i don't understand what is really happening :-( Sorry for previous comment, i was wrong... I think your idea is good ("reparent" the GUI objects depending on BookmarkProvider to the MainWindow they belong.) but don't know how this should be done... *** This bug has been marked as a duplicate of bug 269490 *** |