Closed
Bug 398431
Opened 17 years ago
Closed 17 years ago
Loading a new web page, Camino crashed
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: sharakan, Unassigned)
References
()
Details
(Keywords: crash)
Attachments
(1 file)
26.07 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.4) Gecko/20070509 Camino/1.5 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.4) Gecko/20070509 Camino/1.5 I was browsing through the www.doonesbury.com site. When I got to the specified URL, Camino crashed. Reopening, I was able to go to the site no problem. I also noticed that parts of the pages weren't loading properly before the crash. There were layout problems and some pictures weren't displaying properly. After restarting Camino, they all looked good. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. 2. 3. Crash log is attached.
Reporter | ||
Comment 1•17 years ago
|
||
Comment 2•17 years ago
|
||
Without this being reproducible, it's unlikely we'll be able to do much with it. You should upgrade to Camino 1.5.1, however, as it contains a number of security fixes that weren't in 1.5.
Comment 3•17 years ago
|
||
I've noticed recently that the doonesbury site sometimes display badly/incorrectly. But when that happens with Camino, it also happens with Safari and Opera. I suspect they are having server problems or something similar.
As Chris noted, without clear, reproducible steps to trigger the crash, there's very little we can do. If you continue to hit this same crash while browsing doonesbury.com, do let us know--and if you can provide some steps that cause it all the time, please do reopen this bug report. If you continue to have problems with the doonesbury.com pages not loading correctly, please open a separate bug on that. Also, please make sure you've upgraded to Camino 1.5.2; it contains a number of important fixes. Closing this WFM based on the information currently available.
Updated•17 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•