search

venj / theunarchiver

Automatically exported from code.google.com/p/theunarchiver
Other
0 stars 0 forks source link

Progress display breaks after password entry #215

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Since upgrading to 2.1, I've been having issues extracting files from password 
protected .RAR files.

UnArchiver tends to freeze and these pictures show what I see during the 
freeze. After this occurs, 
one has to kill UnArchiver.app with Activity Monitor.app or Command Line.

I also have a crash log that was written to disk around the time these problems 
happen.

I can't give you a file to reproduce this because A.) the file is personal 
pictures of family. B.) The 
cause of this can't be effectively reproduced repeatedly, even when testing the 
same password 
protected file. :(

Original issue reported on code.google.com by Steve.L...@gmail.com on 31 Oct 2009 at 2:35

Attachments:

GoogleCodeExporter commented 9 years ago 
Well, I still need files before I can do anything, because it's not happening 
here.

Also, make *sure* you don't have any haxies or other similar things causing 
problems.

Original comment by paracel...@gmail.com on 4 Nov 2009 at 2:55

GoogleCodeExporter commented 9 years ago 
No haxies for me. Anyways, try this file. I was able to reproduce three times 
in a row without entering a correct 
password. Pick a password and try to extract.

Original comment by Steve.L...@gmail.com on 9 Nov 2009 at 3:39

Attachments:

GoogleCodeExporter commented 9 years ago 
I still can't reproduce this.

However, the crash backtrace reminds me of one bug I encountered, but now I 
can't 
recall if that one was ever in a released version. It was caused by gcc 
miscompiling 
code, if I'm not mistaken.

I think it's best to let this one be until 2.2, and check again then to see if 
it's gone away. 
If it hasn't, post an update.

Original comment by paracel...@gmail.com on 9 Nov 2009 at 5:20

GoogleCodeExporter commented 9 years ago 
I can confirm this issue. Happens with some files only sometimes, and with some 
always.

Original comment by xtc....@gmail.com on 11 Nov 2009 at 4:34

GoogleCodeExporter commented 9 years ago 
@Comment 4

Any chance you could upload a file so the developer can reproduce?

Original comment by Steve.L...@gmail.com on 13 Nov 2009 at 1:21

GoogleCodeExporter commented 9 years ago 
2.2 is released, so please test that and see if the issue is still there.

Original comment by paracel...@gmail.com on 18 Nov 2009 at 2:29

GoogleCodeExporter commented 9 years ago 
Yup I can still reproduce this but not continuously, like before. 

Question. I just remembered a command I used previously to help me learn how to 
chroot programs. It's called 
dtruss. I'm going to start running dtruss on the pid on unarchiver untill I can 
produce the bug again. My 
question is would this help you determine why this is happening? You have any 
other commands that could 
produce information that could possibly lead to a fix?

Original comment by Steve.L...@gmail.com on 18 Nov 2009 at 4:19

GoogleCodeExporter commented 9 years ago 
Ok so I was able to reproduce this when running dtruss.

I first double clicked the archive I wanted to extract. Run the command 'sudo 
dtruss -p PID' and here is the 
output.

Original comment by Steve.L...@gmail.com on 18 Nov 2009 at 10:39

Attachments:

GoogleCodeExporter commented 9 years ago 
Unfortunately the output doesn't seem to contain quite enough data to be all 
that 
useful.

Did you test 2.2 yet?

Original comment by paracel...@gmail.com on 18 Nov 2009 at 10:47

GoogleCodeExporter commented 9 years ago 
Yup, tested 2.2 right after you posted comment #6. Still exists.

Original comment by Steve.L...@gmail.com on 19 Nov 2009 at 9:24

GoogleCodeExporter commented 9 years ago 
Do you have any other machines to test on, to see if it's limited to just some 
configurations?

Original comment by paracel...@gmail.com on 19 Nov 2009 at 9:42

GoogleCodeExporter commented 9 years ago 
No other machines to test on. Sorry.

I would also like to point out 
http://code.google.com/p/theunarchiver/issues/detail?id=219 is very similar to 
this issue.

Original comment by Steve.L...@gmail.com on 19 Nov 2009 at 11:49

GoogleCodeExporter commented 9 years ago 
Issue 234 has been merged into this issue.

Original comment by paracel...@gmail.com on 27 Jan 2010 at 5:12

GoogleCodeExporter commented 9 years ago 
Just thought I'd tell you that a friend of mine (not computer savvy) has the 
same problem. If you're still 
looking for a file with which this problem occurs, take this one for example:

http://rapidshare.com/files/342110319/Th_B_52_s_Th_B_52_s.part1.rar
http://rapidshare.com/files/342126953/Th_B_52_s_Th_B_52_s.part2.rar
http://rapidshare.com/files/342135657/Th_B_52_s_Th_B_52_s.part3.rar

pw: musicjunky

I've also tried to unrar it using Forklift for him, and that worked without a 
glitch.

Original comment by sarkarva...@gmail.com on 28 Jan 2010 at 12:50

GoogleCodeExporter commented 9 years ago 
I have this problem too. Program hangs if password incorrect (it seems).

Original comment by calendrier@jasonw.eu on 8 Sep 2010 at 8:45

GoogleCodeExporter commented 9 years ago 
Which version are you using? Is it reproducible always, or random? Does it 
happen for some archives but not others? If so, can you send me an archive that 
triggers it?

Original comment by paracel...@gmail.com on 8 Sep 2010 at 10:44

GoogleCodeExporter commented 9 years ago 
Issue 303 has been merged into this issue.

Original comment by paracel...@gmail.com on 8 Oct 2010 at 11:33

GoogleCodeExporter commented 9 years ago 
I have the same problem with 2.5. Freezing happens under these conditions:
1) You enter an incorrect password
2) The .rar is corrupt, due to an interrupted download for example

Original comment by ray.wins...@gmail.com on 21 Dec 2010 at 3:38

GoogleCodeExporter commented 9 years ago 
Do you have a file for which this happens every time you try? That would be a 
very useful thing, since I am still unable to reproduce this.

(Also, test it with 2.6, although there probably shouldn't be a difference.)

Original comment by paracel...@gmail.com on 21 Dec 2010 at 4:40

GoogleCodeExporter commented 9 years ago 
This happens with my 2.6 quite often. Upon entering the wrong password, I get 
the blank screen and I have to kill the app to restart it.

Original comment by bigh...@gmail.com on 14 Jan 2011 at 5:06

GoogleCodeExporter commented 9 years ago 
What I need is a way to reproduce the problem. If you can reproduce this on a 
second machine, or with some particular file, that would be of great help.

Original comment by paracel...@gmail.com on 14 Jan 2011 at 5:23

GoogleCodeExporter commented 9 years ago 
Issue 219 has been merged into this issue.

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

GoogleCodeExporter commented 9 years ago 
I've noticed the crash is dependent on the password entered (perhaps its 
length). Running 2.7.1 on OS X 10.6.8. 

To reproduce crash:
1. Begin extraction of attached 'Photo-encrypted.rar' file (its password is 
'blah').
2. Enter 'whatever' into password field.

This will cause the app to crash.

However, entering 'whatever123' as a password will simply throw up an error. 
This hints at the fact that the crash could be dependent on the password length.

Furthermore, please note that this error isn't the "invalid password" error.

Hope this helps!

Original comment by ra...@incrediblebee.com on 19 Aug 2011 at 7:20

Attachments:

GoogleCodeExporter commented 9 years ago 
Oh, interesting. I can actually reproduce that!

I am not sure if it is the same issue as the earlier people reported, but at 
least I have SOMETHING I can fix now.

Could someone else who's reported this bug do the above test, and tell me if it 
causes the same problem they had earlier?

Original comment by paracel...@gmail.com on 19 Aug 2011 at 7:28

GoogleCodeExporter commented 9 years ago 
I can reproduce the crash with the Photo-encrypted.rar file, but it seems 
different from the original issue where the application freezes with messed up 
window graphics. However I was also able to occasionally reproduce the original 
issue with this file as well (but again it's intermittent). Details below.

== Complete application crash ==
- application crashes after entering password (status window disappears, 
process dies)
- crash report is written out to ~/Library/Logs/DiagnosticReports/ 
(EXC_BAD_ACCESS)
- I tried a whole bunch of different variants of "whatever", changing just the 
last letter
- can reproduce *every time* for Photo-encrypted.rar with the following set of 
passwords:
whateve[X|e|g|i|n-u|z] (e.g. "whateveX")
- have not been able to reproduce the issue the remaining passwords in the set 
whateve[a-z]
- was not able to reproduce it on another random encrypted RAR (I only tried 
the password "whatever")

== Status window freeze ==
- after entering password, status window enters one of two states:
 a. window content turns completely white
 b. normal status bar well, icon, etc. appears, but shifted down with a gray bar across the top of the window
- application halts all processing. 0% CPU usage. No spinning beachball. 
Nothing will happen if left in that state for hours.
- I've taken a sample of the application in this state via Activity Monitor and 
attached it to this comment.
- This can only be reproduced *intermittently*.
- I've reproduced this on Photo-encrypted.rar (resulting in both window states) 
as well as dozens of other encrypted RARs.
- Some passwords I've been able to reproduce it with for Photo-encrypted.rar 
are: whataaaa, whatevey, whatevea, whateveR
- I remember one of the passwords I used to reproduce it on one of my RARs was 
8 characters long.

Specific steps I use to try to reproduce the freezing issue:
0. Copy "whatevea" to clipboard.
1. Select RAR in Finder.
2. Press command-down arrow to open the RAR with The Unarchiver.
3. Press command-V to paste the password into the prompt.
4. Press return to continue.
5. Note whether or not the application has frozen (would happen immediately). 
6. Press command-Q to quit, and repeat from step 1.

Mac OS X 10.7.1
The Unarchiver 2.7

Original comment by pche...@gmail.com on 19 Aug 2011 at 9:05

Attachments:

GoogleCodeExporter commented 9 years ago 
Well, I just tested about 20 times with "whatevea" and that exact sequence of 
actions, and I couldn't get it to freeze up once. There still seems to be some 
external factor that is required to trigger it.

Can you test it on another machine, too, and see if it happens there?

Original comment by paracel...@gmail.com on 19 Aug 2011 at 9:35

GoogleCodeExporter commented 9 years ago 
Also, since the crash is apparently a separate issue after all, I filed issue 
384 to track that instead.

Original comment by paracel...@gmail.com on 19 Aug 2011 at 9:38

GoogleCodeExporter commented 9 years ago 
Well! This happened to me for the first time ever just now, so I can finally 
confirm it. Of course, I still can't reproduce it.

Also, it was caused by a zip file, so it is not RAR files in particular that 
are a problem. Also, it was caused by copypasting an incorrect password.

Has it ever happened to anyone entering a correct password? Also, has it 
happened to anyone actually entering a password, rather than copy-pasting it?

Original comment by paracel...@gmail.com on 24 Aug 2011 at 11:34

GoogleCodeExporter commented 9 years ago 
Yes, it has definitely happened to me:
 - with correct passwords
 - when entering a password instead of pasting it
 - on different machines (MBP and Mac mini)
 - both in Snow Leopard and Lion
 - with and without the "Apply to all" option selected

Other notes:
 - I tend to press return instead of clicking the submit button.
 - I tend to type the password quickly and press return immediately afterwards.
 - It *feels* like it is more likely to happen (almost always, in fact) the first time I use The Unarchiver after not having used it for a while (meaning 24h+). That's hard to quantify though. Also the problem continues to happens intermittently regardless of how long it's been since I've used the program.

However, I just tried again and am able to intermittently reproduce the issue 
with photo-encrypted.rar even if I wait a few seconds before pressing return. 
(I'm pressing command-down or command-O to open the file, then typing in the 
password manually, then pressing return.) And FWIW I was also able to reproduce 
it once just now by double-clicking the file instead of using keyboard 
shortcuts to open it.

Original comment by pche...@gmail.com on 24 Aug 2011 at 11:51

GoogleCodeExporter commented 9 years ago 
I may have found one thing that could cause this, finally. It was 
multithreading related so it might be that it triggered more easily depending 
on how many cores you had.

I am going to optimistically call this fixed now, and if it still happens once 
you try the new version, post some more here or in a new issue.

Original comment by paracel...@gmail.com on 27 Sep 2011 at 9:35

GoogleCodeExporter commented 9 years ago 
3.0 alpha 1 is available on the download page now. Anyone who had problems with 
this issue, please grab that and see if it works better.

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

GoogleCodeExporter commented 9 years ago 
I am not certain if this is the same issue, but it continues to occur for me in 
3.0 alpha 1 with rar files from a specific site that caused the password 
display problem earlier.

Here is a sample file: http://www.fileserve.com/file/uxjcqY5 (not my upload)
Password: jpddl

After entering the password, an error appears saying that it cannot extract the 
file, that it is corrupted. Selecting Continue produces a file with a different 
md5 than that decompressed by cli unrar 3.93. However, decompressing the 
enclosed zip file produces the same files.

Original comment by ful...@fastmail.fm on 7 Dec 2011 at 10:46

GoogleCodeExporter commented 9 years ago 
That is definitely an entirely different problem. Please file a new bug for it, 
as it risks being forgotten if it sits here in a closed issue.

Original comment by paracel...@gmail.com on 7 Dec 2011 at 10:52