Closed
Bug 260965
Opened 21 years ago
Closed 21 years ago
mozilla does not respond anymore with CPU using going to 99%
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mimo2, Unassigned)
References
()
Details
(Keywords: qawanted)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.8a4) Gecko/20040921
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.8a4) Gecko/20040921
when going to this page, mozilla does not respond anymore with CPU using going
to 99%
Reproducible: Always
Steps to Reproduce:
1.go to www.courrierinternational.com
2.
3.
Actual Results:
mozilla does not respond anymore, and CPU usage goes to 99%
This seems to be a regression with recent builds only.
I don't have the same problems with moz 1.8a2 on window
Comment 1•21 years ago
|
||
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; @AB_CD@; rv:1.8a4)
Gecko/20040923 Firefox/0.9.1+
I get a 'Beach Ball of Doom' and did a force quit
Comment 2•21 years ago
|
||
We need a minimized testcase, but it looks like the site sets the src of an
iframe in an infinite loop for some reason...
Keywords: qawanted
Comment 3•21 years ago
|
||
I cannot reproduce with a homemade linux aviary build of today.
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 4•21 years ago
|
||
mimo: can you test again? the site worksforme with linux trunk 2005032205.
perhaps they changed the site.
(In reply to comment #4)
> mimo: can you test again? the site worksforme with linux trunk 2005032205.
> perhaps they changed the site.
I've no more problems with my 2005013021 build.
Comment 6•21 years ago
|
||
excellent
resolving WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•