Bug 362314 - crash after close
Summary: crash after close
Status: RESOLVED WORKSFORME
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: 1.13 (KDE Applications 15.12)
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-26 18:05 UTC by RJ
Modified: 2018-11-01 20:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RJ 2016-04-26 18:05:00 UTC
1. Open Marble
2. File->Export map
3. Close file dialog
4. Close application
5. ...
6. Crash

Reproducible: Always



Expected Results:  
Close without crash

Application: marble (marble), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa2fa9e78c0 (LWP 2021))]

Thread 6 (Thread 0x7fa2c700d700 (LWP 2025)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fa2f6cd681b in WTF::TCMalloc_PageHeap::scavengerThread () at wtf/FastMalloc.cpp:2821
#2  0x00007fa2f6cd6859 in WTF::TCMalloc_PageHeap::runScavengerThread () at wtf/FastMalloc.cpp:1989
#3  0x00007fa2ee9dd454 in start_thread (arg=0x7fa2c700d700) at pthread_create.c:334
#4  0x00007fa2efb0ed8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fa2862f8700 (LWP 2026)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fa2f69e5094 in JSC::BlockAllocator::blockFreeingThreadMain () at heap/BlockAllocator.cpp:139
#2  0x00007fa2f6d056b1 in wtfThreadEntryPoint () at wtf/ThreadingPthreads.cpp:195
#3  0x00007fa2ee9dd454 in start_thread (arg=0x7fa2862f8700) at pthread_create.c:334
#4  0x00007fa2efb0ed8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fa285ad8700 (LWP 2027)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fa2f69e60c3 in JSC::GCThread::waitForNextPhase () at heap/GCThread.cpp:81
#2  JSC::GCThread::gcThreadMain () at heap/GCThread.cpp:99
#3  0x00007fa2f6d056b1 in wtfThreadEntryPoint () at wtf/ThreadingPthreads.cpp:195
#4  0x00007fa2ee9dd454 in start_thread (arg=0x7fa285ad8700) at pthread_create.c:334
#5  0x00007fa2efb0ed8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fa2852d7700 (LWP 2028)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fa2f69e60c3 in JSC::GCThread::waitForNextPhase () at heap/GCThread.cpp:81
#2  JSC::GCThread::gcThreadMain () at heap/GCThread.cpp:99
#3  0x00007fa2f6d056b1 in wtfThreadEntryPoint () at wtf/ThreadingPthreads.cpp:195
#4  0x00007fa2ee9dd454 in start_thread (arg=0x7fa2852d7700) at pthread_create.c:334
#5  0x00007fa2efb0ed8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fa284ad6700 (LWP 2029)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fa2f69e60c3 in JSC::GCThread::waitForNextPhase () at heap/GCThread.cpp:81
#2  JSC::GCThread::gcThreadMain () at heap/GCThread.cpp:99
#3  0x00007fa2f6d056b1 in wtfThreadEntryPoint () at wtf/ThreadingPthreads.cpp:195
#4  0x00007fa2ee9dd454 in start_thread (arg=0x7fa284ad6700) at pthread_create.c:334
#5  0x00007fa2efb0ed8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fa2fa9e78c0 (LWP 2021)):
[KCrash Handler]
#6  QString::size (this=this@entry=0x2df4d60) at ../../src/corelib/tools/qstring.h:229
#7  qHash (key=..., seed=1532655853) at tools/qhash.cpp:184
#8  0x00007fa2f07900dd in qHash (seed=<optimized out>, key=...) at tools/qregexp.cpp:3816
#9  QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::findNode (this=this@entry=0x7fa2f0d22790 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder+16>, akey=..., ahp=ahp@entry=0x0) at ../../src/corelib/tools/qhash.h:952
#10 0x00007fa2f0790408 in QHash<QRegExpEngineKey, QCache<QRegExpEngineKey, QRegExpEngine>::Node>::remove (this=this@entry=0x7fa2f0d22790 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder+16>, akey=...) at ../../src/corelib/tools/qhash.h:840
#11 0x00007fa2f0790683 in QCache<QRegExpEngineKey, QRegExpEngine>::unlink (n=..., this=0x7fa2f0d22780 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder>) at tools/qcache.h:62
#12 QCache<QRegExpEngineKey, QRegExpEngine>::trim (m=92, this=0x7fa2f0d22780 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder>) at tools/qcache.h:187
#13 QCache<QRegExpEngineKey, QRegExpEngine>::insert (this=0x7fa2f0d22780 <(anonymous namespace)::Q_QGS_globalEngineCache::innerFunction()::holder>, akey=..., aobject=0x1950630, acost=8) at tools/qcache.h:167
#14 0x00007fa2f078d4fc in derefEngine (key=..., eng=0x1950630) at tools/qregexp.cpp:3831
#15 invalidateEngine (priv=0x1950510) at tools/qregexp.cpp:3887
#16 0x00007fa2f078d62c in QRegExp::~QRegExp (this=0x7fa2fa8205a8 <Marble::GeoString::combiningDiacriticalMarks>, __in_chrg=<optimized out>) at tools/qregexp.cpp:3981
#17 0x00007fa2efa5c89f in __cxa_finalize (d=0x7fa2fa81a450) at cxa_finalize.c:56
#18 0x00007fa2fa07acf3 in __do_global_dtors_aux () from /usr/lib64/libmarblewidget-qt5.so.23
#19 0x00007ffda4b34db0 in ?? ()
#20 0x00007fa2fa830747 in _dl_fini () at dl-fini.c:252
Backtrace stopped: frame did not save the PC
Comment 1 Andrius Štikonas 2016-05-19 20:03:46 UTC
Hmm, the same thing happens with KDE Partition Manager
Comment 2 Andrius Štikonas 2016-05-19 20:05:17 UTC
Related KPM bug: 363294
Comment 3 Andrew Crouthamel 2018-11-01 13:55:58 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrius Štikonas 2018-11-01 20:21:38 UTC
I'll close this bug as I can't reproduce it.

I remember suffering from a very similar bug in KDE Partition Manager which was fixed in Qt 5.7.1. Probably it fixed marble too.