Bug 362965 - DrKonqi crashes opening DrKonqi on every crash...
Summary: DrKonqi crashes opening DrKonqi on every crash...
Status: RESOLVED UPSTREAM
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: 5.6.3
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-12 02:41 UTC by A. Wilcox (awilfox)
Modified: 2018-01-03 02:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description A. Wilcox (awilfox) 2016-05-12 02:41:20 UTC
If I have a crash (such as bug #362964) that causes DrKonqi to display, and then click Report Bug, no matter what action I take DrKonqi crashes during exit with the following backtrace:

Application: drkonqi (drkonqi), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  QGenericAtomicOps<QBasicAtomicOps<4> >::load<int> (_q_value=@0x7f988af2e720: <error reading variable>) at ../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:90
#7  QBasicAtomicInteger<int>::load (this=<optimized out>) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:118
#8  QtPrivate::RefCount::deref (this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:60
#9  QString::~QString (this=<optimized out>) at tools/qstring.h:1053
#10 QRegExpEngineKey::~QRegExpEngineKey (this=<optimized out>) at tools/qregexp.cpp:866
#11 QHashNode<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::~QHashNode (this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qhash.h:237
#12 QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::deleteNode2 (node=0x2912400) at ../../include/QtCore/../../src/corelib/tools/qhash.h:585
#13 0x00007f98998b61b9 in QHashData::free_helper (this=0x228a240, node_delete=0x7f98998e01a0 <QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::deleteNode2(QHashData::Node*)>) at tools/qhash.cpp:491
#14 0x00007f98998e0172 in QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::freeData (x=<optimized out>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qhash.h:621
#15 QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::~QHash (this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qhash.h:342
#16 QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::clear (this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qhash.h:627
#17 QCache<QRegExpEngineKey, QRegExpEngine>::clear (this=0x7f9899c3c5c0 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder>) at tools/qcache.h:119
#18 0x00007f98998df22d in QCache<QRegExpEngineKey, QRegExpEngine>::~QCache (this=0x7f9899c3c5c0 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder>) at tools/qcache.h:87
#19 (anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::Holder::~Holder() (this=0x7f9899c3c5c0 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder>) at tools/qregexp.cpp:3820
#20 0x00007f989914ea88 in __run_exit_handlers (status=0, listp=0x7f98994ac6d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#21 0x00007f989914ead5 in __GI_exit (status=<optimized out>) at exit.c:104
#22 0x00007f9899139797 in __libc_start_main (main=0x415840 <main(int, char**)>, argc=22, argv=0x7ffdd533e2a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdd533e298) at ../csu/libc-start.c:323
#23 0x0000000000415769 in _start ()

I cannot report this using DrKonqi due to bug #354564.  I guess it's all for the best, because then it would be a never ending loop.

Clicking Close without reporting the bug does not crash, so there is a way out.

Reproducible: Always

Steps to Reproduce:
1. Have something crash (not too hard, you can write a simple kf5 app that calls abort() or such I suppose if you provide a report URL).
2. Click Report Bug in the DrKonqi window.
3. Do anything you want - go ahead and report it, or just click Cancel.

Actual Results:  
The application had a segmentation fault with the above stack trace.

Expected Results:  
The application should quit cleanly.
Comment 1 wikispam 2016-05-13 02:00:30 UTC
Same thing happens here.
Comment 2 A. Wilcox (awilfox) 2018-01-03 02:45:35 UTC
This appears to have been fixed upstream in Qt 5.9, and nothing to do with DrKonqi.  Sorry for the noise.