301745 - large CPU usage when on various websites

Status: RESOLVED INVALID

(Camino Graveyard :: General, defect)

Description

[Sam]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050718 Camino/0.9a2
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050718 Camino/0.9a2

Last time I was on Amazon.com, the CPU was running at something like 95% and
when I looked at the activity monitor Camino was doing all the processing. In
the browser window it said the webpage was done loading but my CPU said otherwise.

Reproducible: Didn't try

Comment 1

[Mike Pinkerton (not reading bugmail)]

i'm sure this is a dupe of other issues.

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Attachment: Sample of Camino while sitting on Amazon.com

(In reply to comment #1)
> i'm sure this is a dupe of other issues.

Any suggestion of which ones?

I was able to get this to repro once while sitting on Amazon.com after it was
loaded; at one point, CPU went up to about 100% and Camino was using most of it
and giving me the beachball (I had just been in the prefs, which seems to have
contributed a little).	Here's a sample (the CPU usage was going down by the
time I made it through all the clicks required to sample!), in the event that
helps determine the cause/dupe.

Comment 3

[Simon Fraser [no longer active]]

The sample shows that Camino is completely idle, so isn't useful.

Comment 4

[thekurst]

Camino Version 2005042806 (0.8.4), CPU Usage on OS X 10.4.2 Averages 12% - 14%
Which is pretty high, when loading pages Camino CPU usage goes up to 100% and
hovers there until the page is fully loaded which tends to take a while.

12" PowerBook G4 1.5 Ghz 512MB  

Comment 5

[Simon Fraser [no longer active]]

(In reply to comment #4)
> Camino Version 2005042806 (0.8.4)

Too old. Try a recent trunk build.

Comment 6

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Can you get us any better data or websites where this happens (with Camino 1.0a1
or a recent nightly); if not, we'll have to close this bug.

Comment 7

[Jasper]

Closing bug due to lack of information.