| Summary: | KDevelop crashes when exitting with a Purpose plugin open | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | RJVB <rjvbertin> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | rjvbertin |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | git master | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
RJVB
2017-02-23 09:38:45 UTC
Created attachment 104181 [details]
New crash information added by DrKonqi
kdevelop5 (5.1.40) using Qt 5.8.0
- What I was doing when the application crashed:
The initial report provides a backtrace made when exitting with the Purpose RB plugin dialog still open. The crash also occurs when exitting after closing (cancelling) the plugin dialog:
-- Backtrace (Reduced):
#7 0x00007f877daee41e in qDeleteAll<QList<QObject*>::const_iterator> (end=..., begin=...) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/../../src/corelib/tools/qalgorithms.h:320
#8 qDeleteAll<QList<QObject*> > (c=...) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/../../src/corelib/tools/qalgorithms.h:328
#9 QQmlApplicationEnginePrivate::cleanUp (this=this@entry=0x429bd40) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtdeclarative/src/qml/qml/qqmlapplicationengine.cpp:60
#10 0x00007f877daee498 in QQmlApplicationEngine::~QQmlApplicationEngine (this=0x429bd20, __in_chrg=<optimized out>) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtdeclarative/src/qml/qml/qqmlapplicationengine.cpp:240
#11 0x00007f877daee4b9 in QQmlApplicationEngine::~QQmlApplicationEngine (this=0x429bd20, __in_chrg=<optimized out>) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtdeclarative/src/qml/qml/qqmlapplicationengine.cpp:241
That's interesting, I didn't notice that DrKonqi failed to assign this report to the proper project?! That's because your binary is called 'kdevelop5', while bugzilla only knows 'kdevelop'. Doesn't KCrash provide bug reporting info that should protect against this probably quite common kind of situation? FWIW it might be quite useful anyway to extend DrKonqi with the same project combobox as you find in the Help/Report Bug dialog provided by KCrash. KDevelop is split up in more than 2 subprojects, so even assigning automatically to "kdevelop" is often inappropriate. We have a binary->product mappings file in DrKonqi: https://cgit.kde.org/plasma-workspace.git/tree/drkonqi/data/mappings That would be a good way to initialise the combobox I suggested ;) Seriously, isn't that something you could re-utilise from KCrash? In the meantime I'll try to remember patching that mapping mechanism locally so it also works for executables with an appended 5. Thank you for the crash 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/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |