Bug 212332

Summary:	Ark very bad at handling large archives
Product:	[Applications] ark	Reporter:	aapgorilla <godutchnow>
Component:	general	Assignee:	Harald Hvaal <metellius>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	rakuco
Priority:	NOR	Keywords:	investigated, triaged
Version:	unspecified
Target Milestone:	---
Platform:	Mandriva RPMs
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description aapgorilla 2009-10-29 22:54:19 UTC

Version:            (using KDE 4.3.2)
Installed from:    Mandriva RPMs

Ark (or rather the kio_archive) really can't handle largish archives at all, trying to unpack this archive http://build.chromium.org/buildbot/archives/chromium_tarball.html

just fails, sometimes even locking the system (I can only move the mouse the rest appears frozen), file-roller has no problems with it

Comment 1 Raphael Kubo da Costa 2009-11-22 18:25:26 UTC

Some time ago, I think it crashed with a backtrace similar to bug 215675 when I tried to load the mentioned archive.

However, I tried it again today and the archive loaded fine. Does it always happen to you?

Comment 2 aapgorilla 2009-11-24 12:41:22 UTC

It is not as much that it crashes, just that my system starts to freeze and opening the archive can take a very long time (and as said my system appears frozen)

Comment 3 Raphael Kubo da Costa 2010-03-02 19:47:35 UTC

Is this still valid for you?

Comment 4 Raphael Kubo da Costa 2010-10-21 01:36:09 UTC

Closing while waiting for feedback from the reporter.

Comment 5 Andrew Crouthamel 2018-09-20 21:58:42 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 6 Andrew Crouthamel 2018-10-21 04:58:45 UTC

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!