246368 - airtransat.com website make the browser eat all the CPU

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Hubert Figuiere [:hub]]

User-Agent:       Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.6) Gecko/20040414 Epiphany/1.2.5
Build Identifier: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.6) Gecko/20040414 Epiphany/1.2.5

airtransat.com website make the browser eat all the CPU.
Goto http://www.airtransat.com/fr/0_0.asp (make sure popups are blocked; see bug
246367)
It may warn you about insecure form submission (nasty JavaScript on the
website), then it'll eat all the CPU.


Reproducible: Always
Steps to Reproduce:

Comment 1

[Jesiah S]

I notice we spend alot of time waiting for the server but mozilla used little of
my CPU whiled waiting.  Have you tried a newer plain version of Mozilla?
WFM LInux 2004072607

Comment 2

[Randy J. Anderson]

(In reply to comment #1)
> I notice we spend alot of time waiting for the server but mozilla used little of
> my CPU whiled waiting.  Have you tried a newer plain version of Mozilla?
> WFM LInux 2004072607

Well, guess what, I'm noticing the exact same problem with K-meleon 0.9! 

Comment 3

[Randy J. Anderson]

(In reply to comment #1)
> I notice we spend alot of time waiting for the server but mozilla used little of
> my CPU whiled waiting.  Have you tried a newer plain version of Mozilla?
> WFM LInux 2004072607

Well, guess what, I'm noticing the exact same problem with K-meleon 0.9! 



(In reply to comment #2)

Noticing the same exact same problem with K-meleon 0.9 under Windows XP.
> (In reply to comment #1)
> > I notice we spend alot of time waiting for the server but mozilla used little of
> > my CPU whiled waiting.  Have you tried a newer plain version of Mozilla?
> > WFM LInux 2004072607
> 
> Well, guess what, I'm noticing the exact same problem with K-meleon 0.9! 

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Hubert Figuiere [:hub]]

still occur on Firefox 1.0.6/Linux.

Comment 6

[Andrew Schultz]

try removing the flash plugin if you have it installed.  If not, then the likely
cause is a DHTML animation loop that the page runs continuously.  It sets
properties on various html elements even though nothing seems to actually move.

With linux seamonkey trunk and 1.0 branch builds, it only uses 15%-20% CPU
although it does use ~50% CPU with mozilla 1.7.11 (same layout engine as firefox
1.0.6).  So please retest with firefox 1.5 beta at the link in comment 4.

Comment 7

[Lewis Rosenthal]

This page is poorly written. It doesn't validate (see http://validator.w3.org/check?verbose=1&uri=http://www.airtransat.com/fr/0_0.asp), and in fact, shows more errors than I think I've ever seen for one page. In short, I don't think this is our bug, but rather the webmaster's for airtransat.com. The fact that IE doesn't hog the CPU still doesn't make this our fault (or our bug to fix).

Just my two cents. I'd like to see this closed as WONTFIX.

Lewis

Comment 8

[Wayne Mery (:wsmwk)]

combining comment 6 and comment 7, closing invalid