My favorites | Sign in
Project Logo
Project hosting will be READ-ONLY Wednesday at 8am PST due to brief network maintenance.
                
New issue | Search
for
| Advanced search | Search tips
Issue 33: Crashes after entering Access Key in Leopard
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  mledford
Closed:  May 2007
Type-Defect
Priority-Medium


Sign in to add a comment
 
Reported by jason.ketterman, Apr 03, 2007
What steps will reproduce the problem?
1. Launch S3browser
2. Click File > New Connection...
3. Enter details and hit Connect

What is the expected output? What do you see instead?
Expected output is a new connection. Instead the application crashes.

What version of the product are you using? On what operating system?
1.0.6 / Leopard Build 9A377a

Please provide any additional information below.
I understand this could very well be a Leopard bug, but I thought I would post it here as well in 
case you had not heard of it. I attached a screenshot of the debug window after the crash.
Picture 1.png
464 KB   Download
Comment 1 by olivierg, Apr 03, 2007
Thanks for the report. I cannot test on Leopard presently, but I'll keep this in mind and investigate on Tiger. Is 
this 100% reproducible ?
Status: Accepted
Comment 2 by jason.ketterman, Apr 04, 2007
Yea, it happens every time. It's completely unusable in Leopard, which is a shame because I'd really like to use it.

Is there anyway that I can help get this working? Any ideas from that screenshot on why it would be crashing?
Comment 3 by jason.ketterman, Apr 07, 2007
It has something to do with the KVO-ness in logOperation. I commented out that method and everything else 
seems to be working.
Comment 4 by mledford, Apr 14, 2007
Thanks for the report! I will take a look at this once I have the latest build of Leopard downloaded from 
connect and installed. Once I determine if it's something strange we're doing or a Leopard bug I'll let you 
know so we can all report it to bug reporter.

Does the latest release binary give this error or only self compiled, from svn, on Leopard? Or Both?

Since you commented out a method it sounds like you are working from the svn trunk exclusively...you may 
not so I would like to check.

Thanks!
Comment 5 by mledford, Apr 17, 2007
I do see that it is crashing with the latest version of Leopard.

However, I have been working on some things, operation retries and smarter queue scheduling, that have made 
major changes to the source code. You will be happy to know that these changes have fixed the crasher. 
Unfortunately I can't commit a fix to the trunk since the changes are so pervasive. So hopefully in the next week 
or so I should have all my code commited which includes several bug fixes and the some new enhancements.
Status: Started
Owner: mledford
Comment 6 by mledford, May 03, 2007
I have committed to the trunk and these changes should be available. Please test, verify, and report back on this 
ticket.
Status: Integrated
Comment 7 by mledford, May 03, 2007
Committed in r101.
Comment 8 by olivierg, May 03, 2007
I can't test right now on a Leopard machine, but I'm ok with releasing an update including this one.
Comment 9 by mledford, May 24, 2007
Moving to fixed status.
Status: Fixed
Sign in to add a comment

Hosted by Google Code