Bug 302834 - Add stops responding when asked to display a large archive
Summary: Add stops responding when asked to display a large archive
Status: RESOLVED WORKSFORME
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: 2.17
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Raphael Kubo da Costa
URL: http://developer.android.com/sdk/
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-07-01 14:44 UTC by Christopher Yeleighton
Modified: 2018-10-27 03:46 UTC (History)
1 user (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 Christopher Yeleighton 2012-07-01 14:44:52 UTC
Ark stops responding when asked to display a large archive.  It keeps the CPU busy at 70% and It only resumes after having read and displayed the structure of the archive.

Reproducible: Always

Steps to Reproduce:
  0. Make sure your machine is rather slow.
  1. Download the Android SDK, expand it and install it.
  2. Tell Dolphin to compress the directory android-sdk-linux.
  3. Tell Ark to open android-sdk-linux.tar.gz.
  4. Tell the window manager to close Ark.
Actual Results:  
  2.   444653702 07-01 13:09 android-sdk-linux.tar.gz
  4. The window manager offers to kill Ark because it has stopped responding..

Expected Results:  
   4. Let Ark cancel and quit immediately.
Comment 1 Elvis Angelaccio 2015-10-09 16:22:51 UTC
I can't reproduce it. If I close Ark while is a loading a big archive, the window is closed as expected. Could you test whether the issue still happen, with a more recent version of Ark?
Comment 2 Andrew Crouthamel 2018-09-25 21:39:15 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 3 Andrew Crouthamel 2018-10-27 03:46:41 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!