425304 - Major memory leak and 100 % CPU at aircanada.com

Status: RESOLVED WORKSFORME

(Core :: General, defect)

Description

[IU]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008032605 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008032605 Firefox/2.0.0.11

When attempting to book a flight at www.aircanada.com, selecting certain booking options and clicking "NEXT" at the "Customize Your Departing Flight" page exposes a major memory leak in Firefox.  Memory consumption grows interminably and the browser consumes 100 % CPU during the process.

Reproducible: Always

Steps to Reproduce:
Please follow the below steps EXACTLY:

1. Launch Windows Task Manager
2. Launch Fx and visit www.aircanada.com
3. On the "Welcome aboard" page, select "Canada" and "English" then click "GO"
4. For flight, enter leaving from "YYC" and going to "YYZ"
5. Select a departure date of Aug 1st and return date of Aug 31st then click "SEARCH"
6. Select a departing and returning "Tango" flight, each under "Connecting Flights", then click "CONTINUE"
7. On the "Customize Your Departing Flight" page, leave the defaults and click "NEXT"
8. Observer the Fx process in Windows Task Manager

Actual Results:  
Firefox consumes memory and CPU indefinitely.

Comment 1

[Rick Stockton]

Using a smoketest build from last night, I see the problem happening in Linux too: 95% CPU, and the VMSize increases by about 50MB *per second* on my Athlon-64 3500+ with 2 gigs of physical memory.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008032523 Minefield/3.0b5pre - Build ID: 2008032523

Comment 2

[Rick Stockton]

BTW, I'm using the default (unhacked) "Minefield" UA, and aircanada.com still treated me exactly as described.

Comment 3

[-fullmetaljacket-]

confirmed using str from comment #0

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b5pre) Gecko/2008032609 Minefield/3.0b5pre ID:2008032609

[not sure which component]

Comment 4

[Carsten Book [:Tomcat]]

i will take a look at this today

Comment 5

[Pavlos Touboulidis]

Attachment: reduced testcase

It doesn't always crash on 2008032605, sometimes it just goes from 50MB to ~600MB and then it drops and is responsive again.

Comment 6

[John]

(In reply to comment #5)
> Created an attachment (id=312032) [details]
> reduced testcase
> 
> It doesn't always crash on 2008032605, sometimes it just goes from 50MB to
> ~600MB and then it drops and is responsive again.
> 

Confirmed. Happened to me. >600MB of RAM usage, 100% CPU and then it stabilized after a while back to normal and 45MB or RAM

Comment 7

[Kornel]

Bug confirmed also on:
Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4

In few seconds RAM usage growin' up to ~600 MB and firefox.exe use two CPU cores at 100%. After 6-8 seconds, memory and CPU usage goes down to normal value.

Comment 8

[Carsten Book [:Tomcat]]

Leak Gauge (http://wiki.mozilla.org/QA:Home_Page:Firefox_3.0_TestPlan:Leaks:LeakTesting-How-To)shows no Memory Leak here , but i also can reproduce the high cpu load.

Comment 9

[Jim Jeffery not reading bug-mail 1/2/11]

I can repo the run-away memory, in the statusbar I saw 'Waiting for s0.bluestreak.com  Consumed 99% of memory, if you waint long enough the page will show 'Done' and memory is released. CPU is 100% and on Vista goes Not Responding several times before it either loads the ad, or times out.

In the View Page info for bluestreak I find:
https://s0.bluestreak.com/ix.e?bb&t=21038 
a 1px x 1px image (web-bug?)

Didn't we something similiar with a ad supplier doing this very thing recently? 

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008032705 Minefield/3.0pre Firefox/3.0 ID:2008032705 <-Todays Nightly

Vista HP SP1  

Comment 10

[Pascal T. Lauzier]

Confirmed.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008050509 Firefox/3.0b5

Comment 11

[IU]

I'm no longer able to reproduce this; Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1a2pre) Gecko/20080822033426 Minefield/3.1a2pre.

Is anyone else still able to reproduce this?

Comment 12

[-fullmetaljacket-]

yup seems wfm now.

Comment 13

[Joshua Mitchell (Inactive)]

Issue is Resolved - removing QA-Wanted Keywords - QA-Wanted query clean-up task