Bug 342497 - Opening a zip file, ark started very slow and crashed when closing
Summary: Opening a zip file, ark started very slow and crashed when closing
Status: RESOLVED WORKSFORME
Alias: None
Product: ark
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.19
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Raphael Kubo da Costa
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2015-01-05 06:25 UTC by Gao yang
Modified: 2018-10-27 01:58 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gao yang 2015-01-05 06:25:11 UTC
Application: ark (2.19)
KDE Platform Version: 4.14.3
Qt Version: 4.8.6
Operating System: Linux 3.16.7-7-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Just open a zip file through dolphin, and it took a long time to load, and crashed while closing the window

The crash can be reproduced every time.

-- Backtrace:
Application: Ark (ark), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0afc3e17c0 (LWP 2835))]

Thread 2 (Thread 0x7f0ae5bff700 (LWP 2879)):
#0  0x00007f0af939c3cd in poll () at /lib64/libc.so.6
#1  0x00007f0af591dbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f0af591dcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f0af9b1f0de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#4  0x00007f0af9af0e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#5  0x00007f0af9af1165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#6  0x00007f0af99ee0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x00007f0af9ad2783 in  () at /usr/lib64/libQtCore.so.4
#8  0x00007f0af99f079f in  () at /usr/lib64/libQtCore.so.4
#9  0x00007f0af6e470a4 in start_thread () at /lib64/libpthread.so.0
#10 0x00007f0af93a47fd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f0afc3e17c0 (LWP 2835)):
[KCrash Handler]
#5  0x00007f0af9a837f0 in QProcess::kill() () at /usr/lib64/libQtCore.so.4
#6  0x00007f0afc011e29 in Kerfuffle::CliInterface::doKill() () at /usr/lib64/libkerfuffle.so.4
#7  0x00007f0afc00a311 in Kerfuffle::Job::doKill() () at /usr/lib64/libkerfuffle.so.4
#8  0x00007f0af9f8645c in KJob::kill(KJob::KillVerbosity) () at /usr/lib64/libkdecore.so.5
#9  0x00007f0ae9717b15 in  () at /usr/lib64/kde4/arkpart.so
#10 0x00007f0ae9717b79 in  () at /usr/lib64/kde4/arkpart.so
#11 0x00007f0af9b08ae8 in QObjectPrivate::deleteChildren() () at /usr/lib64/libQtCore.so.4
#12 0x00007f0afa54c437 in QWidget::~QWidget() () at /usr/lib64/libQtGui.so.4
#13 0x00007f0afa93f129 in QSplitter::~QSplitter() () at /usr/lib64/libQtGui.so.4
#14 0x00007f0afbb185a6 in KParts::Part::~Part() () at /usr/lib64/libkparts.so.4
#15 0x00007f0ae97001b4 in  () at /usr/lib64/kde4/arkpart.so
#16 0x00007f0ae9700209 in  () at /usr/lib64/kde4/arkpart.so
#17 0x000000000040e5bf in _start ()

Reported using DrKonqi
Comment 1 Raphael Kubo da Costa 2015-01-05 12:40:41 UTC
Was it a particularly big file? Can you install debug symbols for Ark and post a new backtrace? I suspect this is bug 341187, which has already been fixed.
Comment 2 Elvis Angelaccio 2015-10-26 21:53:22 UTC
No answer for a long time. Marking as NEEDSINFO.
Comment 3 Andrew Crouthamel 2018-09-25 21:57:26 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 01:58:24 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!