Closed
Bug 424793
Opened 17 years ago
Closed 17 years ago
Camino hangs when accessing mail.google.com gmail
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: amounce, Unassigned)
Details
Attachments
(1 file)
7.85 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_2; en-us) AppleWebKit/525.13 (KHTML, like Gecko) Version/3.1 Safari/525.13
Build Identifier: Camino 1.6 Beta 2
Camino 1.5.5 and 1.6 beta 2 hang when accessing http://mail.google.com
Reproducible: Always
Steps to Reproduce:
1. go to url http://mail.gmail.com
2.
3.
Actual Results:
camino hangs (beachball)
Expected Results:
successfully render the page
Activity monitor sample attached
Comment 2•17 years ago
|
||
It's hanging inside of Apple's Keychain code, which means that this is a system problem on your machine, so there's nothing we can do about it in Camino. It may be a damaged keychain, so you could try running Keychain's first aid command or removing your saved Gmail password; if that doesn't work it may be a system framework itself that's damaged.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Comment 3•17 years ago
|
||
(Another possibility is that securityd is wedged; if you haven't already, try rebooting)
Thanks for the reply. So I tried keychain repair - No problems found by utility, problem still exists. I also did a verification of all of my user and system .plist files, and no problems were found, problem still exists. I also have rebooted several times to no avail.
Interestingly, I have reverted to Camino Version 2007022813 (1.0.4) and this problem does not manifest at all.
Comment 5•17 years ago
|
||
Camino 1.0.x uses completely different (older) keychain APIs, which take different code paths through the system Keychain frameworks, so that's not surprising. And depending on when the gmail entry was last modified, Camino 1.0.4 might not even be able to find it to try to read it.
You didn't mention whether you tried deleting the keychain entry entirely; developers of other Mac applications have seen hangs like this as well, and have reported that in some cases where Keychain first aid didn't show any issues, deleting the entry fixed the problem. Apparently Keychain first aid can't find certain kinds of corruption.
If that doesn't help either, then the Apple discussion forums at <http://discussions.apple.com/> are probably the best place to get help troubleshooting your system issue.
Well, you were 100% correct in your analysis. I deleted the keychain entries, re-installed Camino 1.5.5 and all is well. Thanks for your excellent and timely advice!
Updated•17 years ago
|
Status: RESOLVED → VERIFIED
Comment 7•16 years ago
|
||
I have started getting hangs with Camino 1.6, they did not occur with Camino 1.5.x... one of the items in the 1.6 release notes was better integration with Safari keychains. Keychain First Aid is reporting no problems, and I am extremely reluctant to start removing keychain entries... there is too much critical information in my keychain.
Comment 8•16 years ago
|
||
Camino 1.6 will potentially read more entries than 1.5.x did. If your sample is the same as the one here, then deleting the damaged entry is probably your only option.
Comment 9•16 years ago
|
||
The problem does not seem to be related to Camino 1.6. Coincidentally at the same time I switched to Camino 1.6, I started a new job at a location where I need to use a PAC file to access the net, and the problem seems to be Bug 235853.
You need to log in
before you can comment on or make changes to this bug.
Description
•