Closed
Bug 313127
Opened 19 years ago
Closed 19 years ago
Camino becomes unstable after appearing to render specific Web site correctly
Categories
(Camino Graveyard :: Page Layout, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: thebrix, Assigned: mikepinkerton)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
Build Identifier:
The London Underground real-time travel information site
http://www.tfl.gov.uk/tfl/realtime/default.asp appears to load correctly (no
visible page rendering faults or similar) but, on trying to use links on the
page, fails with Camino becoming unstable and eventually having to be force-quitted.
Reproducible: Always
Steps to Reproduce:
1. Load http://www.tfl.gov.uk/tfl/realtime/default.asp on the latest nightly
build (20051017 build tested, but it has been there for at least a week, when
the London Underground site design changed).
2. Attempt to perform operations on the above, most commonly selecting
individual London Underground lines under the "Current Tube network status" heading.
Actual Results:
Camino immediately becomes unstable, with CPU usage rising to 100 per cent.
Eventually have to Force Quit the application, which OS X 10.4.2 recognises as
requiring to be quit.
Expected Results:
Opened other links on site without any unexpected impact on the browser or system.
No special configuration - nightly build is "out of the box".
|
Assignee | |
Comment 1•19 years ago
|
||
simon, is this the same recursive view bug? why all the recent regressions?
|
||
Comment 2•19 years ago
|
||
I think something in gecko (the view manager?) changed on the branch fairly
recently.
Depends on: 312563
|
|
||
Comment 3•19 years ago
|
||
I don't think this is bug 312563: I can't actually reproduce the instability
here. It does eat CPU, but that's because of the scrolling text at the top of
the page (maybe tickling bug 166932).
Some more testing and regression analysis would be useful here.
I see what Simon sees (in comment 3) here on 10.3.9, Camino 2005101904
(v1.0a1+). We jump to between 75-85% CPU when the ticker starts scrolling, but
in the little bit before that, we were only 35% or so.
I navigated around the site a bit and never got Camino to hang. Things were a
little slow, and I did get the beachball momentarily when trying to select this
bug from the back button's menu, but that's the ticker taking up CPU again, I think.
Reporter, what CPU do you have in your Mac and how much RAM do you have?
|
Reporter | |
Comment 5•19 years ago
|
||
It's an April 2004 PowerBook - G4 1.33GHz, 768MB RAM
Reporter, can you take a sample when the site causes Camino to hang, and attach
it to this bug; see http://www.caminobrowser.org/support/sup_bugzilla.html for
instructions.
Mike/Simon: as for regression, in bug 308802 comment 12, Steven identified the
regression window for the first known recursive widget crash; unfortunately, it
was a period where there were no builds for several days, bet. 9-30 and 10-04.
Bonsai: http://tinyurl.com/apnmh
But again, recursive widget doesn't seem to be the issue here, since the rip-out
patch won't be in a branch build until the 21st, and both the reporter's build
and the ones I'm testing in (19th/20th) have the initial fix from bug 312563.
|
|
Reporter | |
Comment 7•19 years ago
|
||
The problem appears to have been resolved (build 20051020) - I am not seeing the
very high CPU usage or slowness in navigation now ...
OK; must have been some other Gecko change, then. There's already a bug that
touches on the issue of scrolling thing causing slowdowns, so resolving this WFM.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•