428455 - Camino becomes VERY slow and is completely hogging one CPU.

Status: RESOLVED INCOMPLETE

(External Software Affecting Firefox Graveyard :: Flash (Adobe), defect)

Description

[Jamie Kahn Genet]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.15pre) Gecko/20080408 Camino/1.6b5pre (like Firefox/2.0.0.15pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.15pre) Gecko/20080408 Camino/1.6b5pre (like Firefox/2.0.0.15pre)

There's not a lot more I can say. I typically have a few dozen tabs open at once, but no one site that is obviously a troublemaker, at least not immediately.

I have attached a sample of Camino - while misbehaving - taken by Activity Monitor if that is off any use.

Reproducible: Always

Steps to Reproduce:
1. leave Camino Version 1.6b5pre (1.8.1.15pre 2008040800) or other recent nightly builds running for a day.
2.
3.
Actual Results:  
Camino becomes VERY slow and will completely hog one CPU on my 24" 2.8GHz iMac running Leopard 10.5.2.

Expected Results:  
No slowdown.

I am also experiencing Camino not successfully quitting (it just ends up hanging) approx. 4 out of 5 attempts, necessitating a force quit.

Comment 1

[Jamie Kahn Genet]

Attachment: Sample from Activity Monitor while Camino is hogging one CPU.

Comment 2

[Chris Lawson (gone)]

This sounds a lot like bug 412223, and there's Flash all over the sample.

Comment 3

[Jamie Kahn Genet]

Hmmm, was it known which version of flash 412223's reporter had? I also use Camino under 10.3.9 on an old PPC iMac, but infrequently (mainly I'm on an Intel iMac running 10.5.2 nowadays). I wonder if it will happen there as well I leave it going... *tries this*

Comment 4

[Chris Lawson (gone)]

I was using whatever version of Flash was current at the time, but I'm still seeing the bug occasionally (most recently last week, IIRC) with the version of Flash just prior to the security update this week.

cl

Comment 5

[Jamie Kahn Genet]

Oh, ok. Thank you Chris.

Comment 6

[Chris Lawson (gone)]

Jamie, how's it been holding up the last couple of weeks? More hangs/slowness, or have things been smooth?

Comment 7

[Jamie Kahn Genet]

G'day Chris :-)

I've not had any more slowdowns during normal operation, but I continue to experience frequent hangs upon quitting with the nightly builds.

Comment 8

[Chris Lawson (gone)]

How frequent? Every time? Every other time? One in four?

Are you quitting with windows or tabs open, or do you have everything closed when the hang occurs?

Can you get another sample next time it hangs and see if it pretty much matches the one you've posted already? If not, it might be interesting to see what sort of different things are hanging.

Comment 9

[Jamie Kahn Genet]

Attachment: Crash report I get upon force quitting hung Camino nightly after trying to quit Camino.

This hanging upon quitting happens about 50% of the time lately. Not as often as it used to. No idea why it's decreased. Because I have a slightly different collection of sites open now? I typically have several dozen tabs open that I have Camino auto-save and reopen, BTW.

Comment 10

[Dave Aton]

My experience today. Dual PowerMac G5, 2GB RAM (with about 1GB free): 

Camino 1.6.6 with one window open (Facebook live feed): CPU usage hovers around 50%. With no windows open, it hovers around 10%. (Why??) Cleared cache; no change.

By comparison, Safari 3.2 with Facebook live feed window: CPU usage around 11%.

Comment 11

[Ryan L.]

This happens to me too. I leave camino on for long periods of time and after a while it begins to eat up cpu like crazy. It gets up to 70%+ and I have to force quit it because I don't want to wait and let it quit on its own after hanging for 10 minutes. Please fix. I've never used the stable version of camino, only the nightlys and now 2.0b1, so I don't know if it's just problem with that. But I doubt it is. I bet it would do it on the stable version too. Please fix. I'll do what I can to help if you need any info such as crash reports.

Comment 12

[Ryan L.]

(In reply to comment #11)
> This happens to me too. I leave camino on for long periods of time and after a
> while it begins to eat up cpu like crazy. It gets up to 70%+ and I have to
> force quit it because I don't want to wait and let it quit on its own after
> hanging for 10 minutes. Please fix. I've never used the stable version of
> camino, only the nightlys and now 2.0b1, so I don't know if it's just problem
> with that. But I doubt it is. I bet it would do it on the stable version too.
> Please fix. I'll do what I can to help if you need any info such as crash
> reports.

iMac G5 2.0Ghz, 1.5GB RAM -- Camino also uses around 600MB RAM often. Wtf?

Comment 13

[Benjamin Smedberg]

I'm closing a lot of bugs which are filed as Adobe Flash bugs which are either irrelevant, not actionable, or not serious enough to track in the Mozilla bug tracker. For the most part, Flash bugs should be filed in Adobe bugbase, and we'll only track a few highly-critical issues in the Mozilla tracker.

Comment 14

[BMO Automation]

Version and milestone values are being reset to defaults as part of product refactoring.