Bug 298240

Summary: Ark Crashes (or does it?)
Product: [Applications] ark Reporter: Mark Rooks <rooksy>
Component: generalAssignee: Raphael Kubo da Costa <rakuco>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: triaged
Priority: NOR    
Version: 2.18   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Mark Rooks 2012-04-16 11:52:21 UTC
Application: ark (2.18)
KDE Platform Version: 4.8.1 (4.8.1)
Qt Version: 4.8.0
Operating System: Linux 3.3.1-5.fc16.i686.PAE i686
Distribution: "Fedora release 16 (Verne)"

-- Information about the crash:
- What I was doing when the application crashed:I was archiving an .iso (7.4GB full size) to a USB thumb drive of 8GB.

The archiving looks like it is still contiuing even though I got the crash. I will update the bug if the archiving finishes succesfully but thought it worth filing this anyway.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Ark (ark), signal: Aborted
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb773b780 (LWP 17188))]

Thread 2 (Thread 0xb610eb40 (LWP 17190)):
[KCrash Handler]
#7  0xb7777424 in __kernel_vsyscall ()
#8  0x4b53598f in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9  0x4b5372d5 in __GI_abort () at abort.c:91
#10 0x412f6ead in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#11 0x412f4c24 in __cxxabiv1::__terminate (handler=0x412f6d60 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:40
#12 0x412f4c60 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:50
#13 0x412f4daf in __cxxabiv1::__cxa_throw (obj=0xb5801b90, tinfo=0x41327b20, dest=0x412f2d70 <std::bad_alloc::~bad_alloc()>) at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:83
#14 0x415b2653 in qBadAlloc () at global/qglobal.cpp:1991
#15 0x415deab1 in QListData::detach (this=0x843ec78, alloc=-1249902368) at tools/qlist.cpp:186
#16 0x421db29b in ?? () from /usr/lib/libkerfuffle.so.4
#17 0x421dac3c in ?? () from /usr/lib/libkerfuffle.so.4
#18 0x421dc192 in Kerfuffle::Job::onFinished(bool) () from /usr/lib/libkerfuffle.so.4
#19 0x421dae54 in Kerfuffle::ReadOnlyArchiveInterface::finished(bool) () from /usr/lib/libkerfuffle.so.4
#20 0x421dbb08 in Kerfuffle::ListJob::doWork() () from /usr/lib/libkerfuffle.so.4
#21 0x421dc366 in Kerfuffle::Job::Private::run() () from /usr/lib/libkerfuffle.so.4
#22 0x415be0b1 in QThreadPrivate::start (arg=0x841cd10) at thread/qthread_unix.cpp:298
#23 0x4b6bccd3 in start_thread (arg=0xb610eb40) at pthread_create.c:309
#24 0x4b5f9a2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 1 (Thread 0xb773b780 (LWP 17188)):
#0  0xb7777424 in __kernel_vsyscall ()
#1  0x4b6c085c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:172
#2  0x415be638 in wait (time=4294967295, this=0x8446140) at thread/qwaitcondition_unix.cpp:86
#3  QWaitCondition::wait (this=0x8446290, mutex=0x8446274, time=4294967295) at thread/qwaitcondition_unix.cpp:158
#4  0x415bdc49 in QThread::wait (this=0x841cd10, time=4294967295) at thread/qthread_unix.cpp:651
#5  0x421db553 in Kerfuffle::Job::~Job() () from /usr/lib/libkerfuffle.so.4
#6  0x421de15e in Kerfuffle::ListJob::~ListJob() () from /usr/lib/libkerfuffle.so.4
#7  0x416e7502 in QObjectPrivate::deleteChildren (this=0x843a8e8) at kernel/qobject.cpp:1908
#8  0x416edc0a in QObject::~QObject (this=0x843e880, __in_chrg=<optimized out>) at kernel/qobject.cpp:927
#9  0x421def31 in Kerfuffle::ArchiveBase::~ArchiveBase() () from /usr/lib/libkerfuffle.so.4
#10 0x421def63 in Kerfuffle::ArchiveBase::~ArchiveBase() () from /usr/lib/libkerfuffle.so.4
#11 0xb652e3ec in ?? () from /usr/lib/kde4/arkpart.so
#12 0xb652e453 in ?? () from /usr/lib/kde4/arkpart.so
#13 0x416e7502 in QObjectPrivate::deleteChildren (this=0x8387460) at kernel/qobject.cpp:1908
#14 0x416edc0a in QObject::~QObject (this=0x82f50f0, __in_chrg=<optimized out>) at kernel/qobject.cpp:927
#15 0x42f89145 in KParts::Part::~Part (this=0x82f50f0, __vtt_parm=0xb65414cc, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/kparts/part.cpp:190
#16 0x42f8c0dd in KParts::ReadOnlyPart::~ReadOnlyPart (this=0x82f50f0, __vtt_parm=0xb65414c8, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/kparts/part.cpp:460
#17 0x42f8c221 in KParts::ReadWritePart::~ReadWritePart (this=0x82f50f0, __vtt_parm=0xb65414c4, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/kparts/part.cpp:773
#18 0xb651e0ce in ?? () from /usr/lib/kde4/arkpart.so
#19 0xb651e143 in ?? () from /usr/lib/kde4/arkpart.so
#20 0x080541cc in _start ()

Possible duplicates by query: bug 296425, bug 296407, bug 293802, bug 292249, bug 289446.

Reported using DrKonqi
Comment 1 Raphael Kubo da Costa 2012-04-16 14:05:31 UTC
Can you install Ark's debug symbols and post a more detailed backtrace?
Comment 2 Raphael Kubo da Costa 2012-05-08 15:09:52 UTC
Closing while waiting for feedback.
Comment 3 Andrew Crouthamel 2018-09-23 02:33:22 UTC
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 set the bug status 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!
Comment 4 Andrew Crouthamel 2018-10-27 03:39:07 UTC
Dear Bug Submitter,

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!