[kde] [Bug 376835] KDevelop crashes when exitting with a Purpose plugin open
RJVB
bugzilla_noreply at kde.org
Thu Feb 23 09:42:51 GMT 2017
https://bugs.kde.org/show_bug.cgi?id=376835
--- Comment #1 from RJVB <rjvbertin at gmail.com> ---
Created attachment 104181
--> https://bugs.kde.org/attachment.cgi?id=104181&action=edit
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 at 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
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list