Bug 385323

Summary: The process of unpacking a .bz2 file using ark doesn't finish, resulting in a huge unpacked file
Product: [Applications] ark Reporter: mikefarmer02
Component: generalAssignee: Elvis Angelaccio <elvis.angelaccio>
Status: RESOLVED FIXED    
Severity: normal CC: rthomsen6
Priority: NOR    
Version First Reported In: 16.08.3   
Target Milestone: ---   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description mikefarmer02 2017-10-03 12:21:58 UTC
Multiple times, I tried to unpack a .bz2-archive using ark. The process of unpacking doesn't stop, so I stopped it manually when the size of the unpacked file was about 10 times bigger than it should be.
Comment 1 Elvis Angelaccio 2017-10-03 12:36:15 UTC
I can't reproduce, we need more info about the issue.

Does it happen with every bz2 archive? If not, can you attach a test archive?
Comment 2 mikefarmer02 2017-10-03 13:13:09 UTC
(In reply to mikefarmer02 from comment #0)
> Multiple times, I tried to unpack a .bz2-archive using ark. The process of
> unpacking doesn't stop, so I stopped it manually when the size of the
> unpacked file was about 10 times bigger than it should be.

"about 10 times bigger than the .bz2-archive" rather
Comment 3 mikefarmer02 2017-10-03 13:15:51 UTC
Unpacking the archive with "bzip2 -d" gives me the same behaviour.

Maybe this is just how big the unpacked file would be? I don't know the compression rates of bzip2..
Comment 4 mikefarmer02 2017-10-03 13:23:26 UTC
(In reply to Elvis Angelaccio from comment #1)
> I can't reproduce, we need more info about the issue.
> 
> Does it happen with every bz2 archive? If not, can you attach a test archive?

Unpacking a smaller .bz2-archive (~100MB) from the same website results in a 1,2GB file. 
So the original 5GB-archive would result in a 60GB file, which means I stopped the process to early.

Thanks for your help and I'm sorry I bothered you unnecessarily..
Comment 5 mikefarmer02 2017-10-03 13:24:08 UTC
Did I choose the right status (RESOLVED INVALID) for the bug report btw?
Comment 6 Elvis Angelaccio 2017-10-03 13:25:19 UTC
(In reply to mikefarmer02 from comment #5)
> Did I choose the right status (RESOLVED INVALID) for the bug report btw?

Yes.

For the record, in Ark you can open "Archive -> Properties" which should tell you the compression ratio of the archive.
Comment 7 mikefarmer02 2017-10-03 13:45:05 UTC
(In reply to Elvis Angelaccio from comment #6)
> (In reply to mikefarmer02 from comment #5)
> > Did I choose the right status (RESOLVED INVALID) for the bug report btw?
> 
> Yes.
> 
> For the record, in Ark you can open "Archive -> Properties" which should
> tell you the compression ratio of the archive.

Thanks. For both archives tested, the properties for file size (uncompressed) and compression rate are 0B/0.0 though.