744176 - Memory leak or incorrect behavior, probably in javascript handling

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[Marius Hudea]

Attachment: memory.zip

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0
Build ID: 20120312181643

Steps to reproduce:

Browsing an image gallery on a website, clicking Next to move from picture to picture.
Firefox was using about 400 MB of memory, after about 10-15 pictures viewed, clicking on Next to get the next picture.


Actual results:

About half way into the page load it started to use more and more memory until about 10-15 seconds later it stopped at about 1.5 GB of memory. 
It's now at 1.5 GB and slowly increases by about 200 KB/s.

Oh I'm not sure if it matters but after this memory increase the status bar was saying on the page that triggered it "connecting to [url]..." - not sure if the domain was unresponsive or it was a consequence of this issue.


This happened once again a few hours earlier but the trigger was simply clicking on Full Screen button of a Youtube video, Then, it went up to 2.3 GB of memory or so and after about 30 seconds of freezing, it went back to 300-400 MB of memory usage.

I managed to open a new tab and entered about:memory - I'm attaching here the "more verbose" text dump. When it happened for the first time, I used "Save as page" but no text was saved, so I just selected all text and pasted it into Notepad this time.


Expected results:

Not get tabs frozen or memory go up by 1 GB and stay there...

Comment 1

[Nickolay_Ponomarev]

Attachment: about:memory dump from the reporter

Comment 2

[Nickolay_Ponomarev]

The about:memory dump shows:
1500 MB explicit, major contributors are:

400  MB compartment(http://www.head-fi.org/gallery/album/view/id/21715/user_id/168345)
150  MB compartment([System Principal], 0x6077000)
600  MB heap-unclassified
100  MB images

I don't get this on my main profile (with adblock and others) on a nightly, but I see this on a clean profile with firefox 11.

Comment 3

[Nickolay_Ponomarev]

I get this on Google Chrome as well (clicking on the first image in the gallery at the head-fi.org URL listed in comment 2), so it's likely a problem with the website. Any reason you didn't think so?

The general "websites shouldn't be able to bring down Firefox" idea is covered by other bugs.

Comment 4

[Phoenix]

Resolved per whiteboard