407167 - keychain access fails

Status: RESOLVED INCOMPLETE

(Camino Graveyard :: OS Integration, defect)

Description

[Jerry]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.11pre) Gecko/20071206 Camino/1.6a1pre (like Firefox/2.0.0.11pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.11pre) Gecko/20071206 Camino/1.6a1pre (like Firefox/2.0.0.11pre)

first attempt to access keychain after updating to 1.5.4 ask to premission aw with every update. i checked allow cpu usage went to 100% memory usage went to 90% and never released the memory. Camino hangs and never finishes loading the page and heas to be force quit. memory usage remains at 90% causing me to have to restart my computer to be able to use it. after restart i tried again and same thing happened. tried latest nightly build and same thing habbens. this does not happen with other programs that access keychain.

Reproducible: Always

Steps to Reproduce:
1.restarted computer
2.tried accessing a different site that requires a login
3.updated software to latest nightly build
Actual Results:  
same thing Camino hangs leaving 90% of memory on my mac in use

Expected Results:  
access keychain and loginto site

Comment 1

[Chris Lawson (gone)]

Can you get a sample

http://caminobrowser.org/documentation/bugzilla/#hang

and post it as an attachment (using the "Add an attachment" link) here?

cl

Comment 2

[Stuart Morgan]

(In reply to comment #0)
> [...] after updating to 1.5.4

From what version?

This sounds like most likely part of your keychain is corrupt or damaged, so you should try running Keychain first aid from within the Keychain Access application.

Comment 3

[Jerry]

what logic are you using to come to that conclusion????
1. previous version of camino did not do this
2. i stated in my post that no other apps using keychain were having any problems

here is the result of keychain firstaid
Verification started
Checking keychain configuration for Jerry Clayton (user ID=501)
Home directory is /Users/jerryclayton
Checked login keychain
Checked default keychain
Checked contents of ~/Library/Keychains/login.keychain
No problems found
Verification completed

the issue is with cmino not my mac

Comment 4

[Jerry]

previous version was 1.5.3

Comment 5

[Stuart Morgan]

(In reply to comment #3)
> what logic are you using to come to that conclusion????

Partly the fact that you said you still had problems with your computer *after* you force-quit Camino; once Camino is not running, it by definition cannot be using either CPU or memory, so a persistent problem suggests an issue in something that's part of the system, and therefore still running. Partly the fact every single time someone has had a hang trying to access keychain, it's been deep in the keychain code, due to a problem with the keychain.

> 1. previous version of camino did not do this

Absolutely nothing about the keychain code in Camino has changed between 1.5.4 and 1.5.3. The difference is most likely that 1.5.3 was already authorized for the stored passwords, whereas 1.5.4 wasn't, so different code inside of the Keychain framework is being run when you use 1.5.4.

When you say "the same thing happened" after you restarted, does that include the Keychain prompt to allow the new version of Camino to access keychain, despite your already having allowed it the last time?

> 2. i stated in my post that no other apps using keychain were having any
> problems

Have you upgraded them, triggering an authorization dialog? Are they trying to access the same keys Camino is? Unless the answer to both questions is yes, then they aren't exercising the same code in Keychain or reading the same part of the data store.


A few more things to try:
1) First, please do get the sample of Camino in the hung state, as requested in comment 1
2) Please use Activity Monitor to see what process is responsible for the problem you are still seeing after force-quitting Camino (I'm not sure what you mean exactly by memory being at 90%, since there isn't really a limit to available virtual memory in most circumstances)
3) If you try to store a password on a new site, rather than visiting a site with an existing login, what happens? (You can just make up a name and password on a site where you don't have an account, to trigger the option to save it)
4) If you manually remove Camino's authorization access from one of your accounts (using Keychain Access) and then visit that site, and you Allow Once what happens? How about Always Allow?

Comment 6

[Phil Giltner]

I have the keychain problem, also: (note that the cpu usage not apparently an issue for me). Installed 1.5.4 on two macs (G3 500mhz ibook & g4 12" 1Ghz PB), and now etrade & my bank accounts do not access keychains for login id or passwords. These worked just fine in 1.5.3. Have performed keychain first aid (nothing found) &  run applejack on both machines. Have tossed camino plist, restarted, & usual troubleshooting routines. 

Perhaps a clue here: only once when loading bank's page in background, camino growl tells me that the page failed to load, even though it visually seems to have loaded. 

When going to my bank, entering id & password, camino does not ask if i want to store passwords.

Comment 7

[Stuart Morgan]

Phil, please file a new bug, as if you aren't seeing a hang, you don't have the same issue as the reporter.

Comment 8

[Stuart Morgan]

Jerry, could you answer the questions in comment 5 please? There's nothing we can do here without more information.

Comment 9

[Jerry]

(In reply to comment #8)
> Jerry, could you answer the questions in comment 5 please? There's nothing we
> can do here without more information.
> 
I am sorry but I do not have time to deal with this. The attitude you have tken from the start is that it could not possibly be a issue with Camino really tickes me off!!! I have always loves this program and recommended it to everyone. First time I have an issue i am treated like an dummy.

By the way id do hardwar and software support for 3 different telecomm switches (Lucent, NOrtel, & Ericsson) so i am not a dummy and did not submit the bug until I had tested. No other new updated program is causing the issue.

I do not have time to help with data gathering because my wife of 32 years has been diagnosed with Leukemia.

It looks like I am not the only dummy out here after all since others are having the same issue.

Comment 10

[Stuart Morgan]

(In reply to comment #9)
> The attitude you have tken from the start is that it could not possibly be a
> issue with Camino really tickes me off!!!

That's not at all my attitude. I asked you to try repairing the keychain because it's an easy and useful way to eliminate one possible source of problems (one which has been the issue for other users with similar symptoms in the past). I explained how it was possible for it not to be a Camino bug despite the behaviors you were seeing because you asked specifically, not because I was trying to prove that it must be the case. All I was trying to do was answer the question you asked; I'm sorry that upset you.

The reason I asked you to do some specific tests was to help determine one way or the other whether it was a Camino bug or a system bug; I wouldn't have done that if I had already made up my mind.

> First time I have an issue i am treated like an dummy.

I don't know where you got that impression, but I'm sorry you feel that way. I wasn't asking questions to try to prove you wrong or because I don't believe that it's a real problem for you, but to get more information. Since you've done support, I'm sure you understand that getting detailed information from people actually experiencing the issue is the only way to solve a problem that can't be reproduced locally (and I did try to reproduce this myself). All of the tests I asked you to do were to help isolate the specific Camino and system code involved in the hang.

> others are having the same issue.

That may well be true, but none that we are aware of; Phil's problem was not this at all (and turned out not to be a Camino bug, but a pref that needed to be set), and no-one else has reported any problems with the keychain in 1.5.4 via bugzilla, email, or the forums, and as I said I can't reproduce it on any of my machines.

Again, I don't doubt at all that you are having the problem you describe, or that it's possible that it's a Camino bug that happens in an edge case we haven't found before. Unfortunately, without access to anyone else having the issue, and with you unable to help us narrow it down due to your unfortunate personal circumstances, we can't debug it further at this point. If anyone else shows up with the same problem, we'll update this bug with whatever we find, but for now we'll have to close it since there's no way for us to progress.