Closed Bug 792895 Opened 12 years ago Closed 12 years ago

firefox crashes while loading an url (memory goes up to 100%)

Categories

(Core :: Graphics: ImageLib, defect)

16 Branch
x86_64
Linux
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 661304

People

(Reporter: costamagnagianfranco, Unassigned)

References

()

Details

(Keywords: hang)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0
Build ID: 20120912185722

Steps to reproduce:

If you look at xkcd.com the latest image is really really big
http://xkcd.com/1110/

somebody [1] took the entire set of pictures and stored in a single html page [2]

[1] http://blackhole12.blogspot.it/2012/09/analyzing-xkcd-click-and-drag.html
[2] http://blackspherestudios.com/storage/xkcd_huge_static.html


Actual results:

if you visit with firefox 16 the url [2] firefox will enter in a memory leak until 100% and the OS will kill it.

OS ubuntu 12.04 LTS x64


Expected results:

Firefox shouldn't crash
Without testing the URL: Many big images on a page are consuming a huge amount of memory during decoding. Why should there be a memory leak involved ?

It's basically also no crash if the OS kills the process die to OOM
Severity: normal → critical
Keywords: hang
This is true, this is not a crash, but for the end user is almost the same...

This is a problem since I can open the url with chrome and I have NO problem at all.

I have 4GB of ram and 1 GB swap, trust me, this seems to be not only an image loading, the image according to url is not so big :)
No crash/hang on latest win32 m-c hourly build:
cset: https://hg.mozilla.org/mozilla-central/rev/f8d30ea0974c

win7 x64 8gig RAM

Firefox is using 2x the memory of IE9 on link 2
Fx: 3.58gig
IE: 1.65gig

Both browsers open on the same image at the same time, no crash/hang.

As expected, Firefox dumped the image when switching away from the tab, and fell back to pre-image loads values of ~450meg.

Switching back to the image tab took several seconds, I would think expected, with a brief period of not-responding. 

Other than proving some sort of point, I see no real value in such an exercise.
More memory used for images compared to other browser is something that can be worked on. There are already other bugs about memory issues like bug 682638/ bug 686905
Component: Untriaged → ImageLib
Keywords: hang
Product: Firefox → Core
I'm going to say this is a duplicate of not-discarding-images-that-arent-visible, but there will probably be some things that we can do even after that's fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
For me, it hangs in Nightly on Windows with 4GB of RAM.
It's OK in IE 9 and Chrome 21.
You need to log in before you can comment on or make changes to this bug.