search

zac-wang / theunarchiver

解压缩Mac项目
Other
2 stars 1 forks source link

The Unarchiver locking up and munching CPU since migration #338

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Since migrating my OS to a new computer (I think. This might be coincidence.), 
The Unarchiver appears to get most of the way through unarchiving archives (any 
and all of them), and locks up and uses all the CPU it can get its hands on. 
I've left it running, but it keeps going until I force quit.

Any idea what might be up? Attached is a sample.

Original issue reported on code.google.com by sid...@s4y.us on 1 May 2011 at 8:47

Attachments:

GoogleCodeExporter commented 8 years ago 
It appears to get stuck while trying to copy the quarantine metadata attributes 
from the archive to the files it extracted. Why is a bit of a mystery.

What filesystem are you using? Anything else unusual about your system that 
could be related to that?

Original comment by paracel...@gmail.com on 1 May 2011 at 9:15

GoogleCodeExporter commented 8 years ago 
Sorry for the lag!

No, unfortunately I can't think of anything special about my system, and I'm 
using plain old JHFS+. The built-in archive utility worked on the same files.

I've since migrated my OS again (new boot drive) and haven't been able to 
reproduce the problem yet. Hmm.

Original comment by sid...@s4y.us on 9 May 2011 at 3:12

GoogleCodeExporter commented 8 years ago 
I also have an issue with Unarchiver using very high amount(above 75%), and 
sometimes all of my CPU. I have been dealing with the issue for a while. It 
happens even if I'm not running any other applications and only archiving one 
file.

I just unarchived a .7z archive that was 1.87 GB. The file was originally split 
into two parts, but was joined earlier today by Unarchiver. The file that was 
previously compressed was a folder that contained a .DMG file.The CPU 
fluctuated, but was definitely consuming at least 2/3 of my CPU in terms of 
percentage. There were many times when it went OVER 100% to something like 115%.

I also migrated from the 250GB hard drive my MacBook came with, to a 1TB 
Western Digital Scorpio Blue hard drive. I currently have latest Snow Leopard 
update, 10.6.7.

Unarchiver.app version 2.5

Here are my specs:

Late 2008 13 inch Aluminum Unibody
2.4 GHz Core 2 Duo
4 GB 1067 MHz DDR3 (upgraded from 2GB)
1TB Western Digital Scorpio Blue 5200rpm (upgraded from 250GB)

Here are the Unarchiver.app preferences:

ARCHIVE FORMATS
-Open these archive types with Unarchiver:
"select all

EXTRACTION
-Extract archives to:
"Same folder as the archive"
-Create a new folder for the extracted files:
"always"
-Set the modification date of the created folder to:
"The current time and date"
-Also set the modification date of single top-level items
     -unchecked, option is also faded
-After successfully extracting the archive:
"open the extracted folder" - unchecked
"move the archive to the trash" - unchecked

ADVANCED
Filename encoding autodetection
-Filename encoding: Detect Automatically
-Threshold: 80% confidence

Hope this information helps.
@s...@sidneysm.com, do we have any common settings or specifications?

Original comment by coogan.g...@gmail.com on 13 May 2011 at 3:40

GoogleCodeExporter commented 8 years ago 
Also, I just realized my version was outdated. I just upgraded to version 2.7.1.

Original comment by coogan.g...@gmail.com on 13 May 2011 at 3:43

GoogleCodeExporter commented 8 years ago 
It still consumes my CPU.

Original comment by coogan.g...@gmail.com on 13 May 2011 at 3:44

GoogleCodeExporter commented 8 years ago 
So what was the exact problem? Did it lock up? At which stage of the 
compression?

Original comment by paracel...@gmail.com on 13 May 2011 at 10:47

GoogleCodeExporter commented 8 years ago 
For me, it fully completed, and I can even remove the decompressed files from 
.TheUnarchiverTemp0 in my Downloads folder. But the bar just stays at 100%, 
displaying the last file decompressed, and a mouse on the window gives me the 
spinning beachball of death.

Original comment by thebenep...@gmail.com on 5 Jul 2011 at 12:30

Attachments:

GoogleCodeExporter commented 8 years ago 
Well, I still need to figure out what triggers it. Can you test on another 
computer? Another disk? Another file?

Original comment by paracel...@gmail.com on 5 Jul 2011 at 12:47

GoogleCodeExporter commented 8 years ago 
This will probably be fixed when issue 254 is fixed, as the new code uses 
another method to copy quarantine metadata which is probably more reliable.

Original comment by paracel...@gmail.com on 9 Aug 2011 at 3:05

GoogleCodeExporter commented 8 years ago 
Going to call this fixed now that issue 254 is fixed, even though I can't test 
it.

Please test it once 3.0 is out (or build from the mercurial repository to test 
now, if you feel like doing that). If it still happens, report back.

Original comment by paracel...@gmail.com on 7 Sep 2011 at 11:56

GoogleCodeExporter commented 8 years ago 
3.0 alpha 1 is available on the download page. Anyone who had this problem, 
please test it and see if it works better.

Original comment by paracel...@gmail.com on 12 Nov 2011 at 6:12

GoogleCodeExporter commented 8 years ago 
I have been unable to use Unarchiver 3.0 on my MacBook Pro running OS X 10.6.8. 
It refuses to unarchive anything, and I have switched back to Zipeg. I used 
Unarchiver preferentially before the current release, but until this issue is 
fixed, I consider it useless.

Original comment by bloommar...@gmail.com on 25 Mar 2012 at 10:52

GoogleCodeExporter commented 8 years ago 
Try the 3.1 alpha, there is a 10.6 bug that has been fixed there.

And please do not post comments on random unrelated bugs.

Original comment by paracel...@gmail.com on 25 Mar 2012 at 11:23

GoogleCodeExporter commented 8 years ago 
Thanks. It works like a charm. MGBMD
Mark Gary Blumenthal, MD, MPH aka Marko Bloom

Original comment by bloommar...@gmail.com on 25 Mar 2012 at 12:33