| Summary: | gwenview crash when closing the program | ||
|---|---|---|---|
| Product: | [Applications] gwenview | Reporter: | Simon Andric <simonandric5> |
| Component: | general | Assignee: | Gwenview Bugs <gwenview-bugs-null> |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | crash | CC: | jaak, oldium.pro |
| Priority: | NOR | ||
| Version First Reported In: | 2.10.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
Gwenview 4.9.4 valgrind output New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Simon Andric
2012-11-16 12:46:29 UTC
Created attachment 75478 [details]
New crash information added by DrKonqi
gwenview (2.9.2) on KDE Platform 4.9.3 using Qt 4.8.2
- What I was doing when the application crashed:
I have a slideshow set on my KDE desktop. I clicked "Open Wallpaper Image" from the desktop popup menu, which opened gwenview with the active wallpaper image from the slideshow. If I closed gwenview, this crash happened.
This crash only appears to occur when Gwenview is in image view mode, not in folder browsing mode.
-- Backtrace (Reduced):
#6 0x000077b34b6ebb45 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x000077b34b6ecfbb in __GI_abort () at abort.c:91
[...]
#11 0x000077b34daf55be in QMetaType::destroy (type=70, data=0x77b329c976c0) at kernel/qmetatype.cpp:1384
[...]
#14 0x000077b34daec8aa in QCoreApplicationPrivate::~QCoreApplicationPrivate (this=0x765a8dfec40, __in_chrg=<optimized out>) at kernel/qcoreapplication.cpp:449
#15 0x000077b34c448b09 in QApplicationPrivate::~QApplicationPrivate (this=0x765a8dfec40, __in_chrg=<optimized out>) at kernel/qapplication.cpp:223
Unfortunately the backtrace is not enough to understand this bug. Is it 100% reproducable for you? Can you try to reproduce the bug while running Gwenview in Valgrind, then post Valgrind output? Created attachment 75755 [details]
Gwenview 4.9.4 valgrind output
I'm unable to reproduce with KDE 4.9.4. However, here's the valgrind output for 4.9.4 anyways. With a weird assertion at the end.
Created attachment 75857 [details]
New crash information added by DrKonqi
gwenview (2.9.2) on KDE Platform 4.9.3 using Qt 4.8.3
- What I was doing when the application crashed:
I opened the gwenview from Midnight Commander as an edit action on an PNG image on local drive (`gwenview %f >/dev/null 2>&1 &`) and closed it afterwards. The program always crashes. I'm doing no navigation between images.
-- Backtrace (Reduced):
#8 0xb593093f in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:63
#9 0xb5932205 in __GI_abort () at abort.c:90
[...]
#13 0xb6f9d55a in qt_assert (assertion=0xb719e352 "qMetaTypeGuiHelper", file=0xb719e33d "kernel/qmetatype.cpp", line=1384) at global/qglobal.cpp:2013
#14 0xb70c79ae in QMetaType::destroy (type=70, data=0xb0204270) at kernel/qmetatype.cpp:1384
[...]
#17 0xb70be8e4 in QCoreApplicationPrivate::~QCoreApplicationPrivate (this=0x957b6c0, __in_chrg=<optimized out>) at kernel/qcoreapplication.cpp:449
I still have 4.9.3, so maybe I can try to run it with Valgring. This is not 100% reproducible. When closed too early, it doesn't crash. When closed too late, it doesn't crash. There is some operation, which isn't terminated or is terminated too late (when other parts are destroyed) during shutdown. I'm not able to catch this moment with Valgrind running. Created attachment 75970 [details]
New crash information added by DrKonqi
gwenview (2.9.4) on KDE Platform 4.9.4 using Qt 4.8.4
- What I was doing when the application crashed:
Same as before - opened the image from Midnight Commander and closed easly. The problem is still there. From last time I've updated the Qt to 4.8.4 and KDE to 4.9.4.
-- Backtrace (Reduced):
#8 0xb590193f in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:63
#9 0xb5903205 in __GI_abort () at abort.c:90
[...]
#13 0xb6fa1015 in qt_assert (assertion=0xb71c9452 "qMetaTypeGuiHelper", file=0xb71c943d "kernel/qmetatype.cpp", line=1384) at global/qglobal.cpp:2018
#14 0xb70e362e in QMetaType::destroy (type=70, data=0x89f6738) at kernel/qmetatype.cpp:1384
[...]
#17 0xb70d9784 in QCoreApplicationPrivate::~QCoreApplicationPrivate (this=0x8496348, __in_chrg=<optimized out>) at kernel/qcoreapplication.cpp:480
Crash (identical backtrace) still present with 4.10.3. Is there some detail in the backtrace from which you could find the problem? I can use gdb to find the detail. Still present with latest gwenview. The core dump contains two threads. One is main() and second one is QInotifyFileSystemWatcherEngine::run. The important information from the Q_ASSERT shown in all backtraces is that the destructor of QApplication has returned and the instance destruction continued by parent class (QCoreApplication) - the qMetaTypeGuiHelper is NULL (set in ~QApplication() as the last step). The destruction continues to queued events (~QCoreApplicationPrivate destroying postEventList) and there is a GUI event (QMetaCallEvent), which needs the qMetaTypeGuiHelper in its destructor. The gdb says that QMetaCallEvent's callFunction is Gwenview::ThumbnailCache::qt_static_metacall(QObject*, QMetaObject::Call, int, void**). Is there anything more I can do in order to investigate the problem? This is what I got from the core dump. I see the status is RESOLVED even though the crash is still here and reproducible. I there is no response, I will create a new bug report. I realised there was no response to my last comment already, so I created bug 321540. |