Closed Bug 659220 Opened 9 years ago Closed 9 years ago
Firefox runs out of memory and crashes when image cache fills up
Probably has to do with the JS engine not really running GC much in this case because it has no idea that the image data exists....
Assignee: nobody → general
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: general → general
Would it be possible to teach the GC that the image data exists? This bug was spun off from bug 653970, which is about problems with image-heavy sites.
> Would it be possible to teach the GC that the image data exists? I have no idea... The fundamental problem is that the <img> element will often keep the data alive... but so will some other stuff. We could give GC an overestimate of the data that might be freed by a GC. Would that be ok?
It looks like bug 658604 is related to this bug.
Here's a crash report: Crash Report ID: ed79b265-e3c0-4133-a301-e5ec82110523 Crashing Thread: 0 mozalloc.dll mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:77 1 mozalloc.dll mozalloc_handle_oom memory/mozalloc/mozalloc_oom.cpp:54 2 xul.dll nsTArray_base<nsTArrayDefaultAllocator>::EnsureCapacity obj-firefox/dist/include/nsTArray-inl.h:106 3 xul.dll nsTArray<char,nsTArrayDefaultAllocator>::AppendElements<char> obj-firefox/dist/include/nsTArray.h:770 4 xul.dll mozilla::imagelib::RasterImage::AddSourceData modules/libpr0n/src/RasterImage.cpp:1257 5 xul.dll mozilla::imagelib::RasterImage::WriteToRasterImage modules/libpr0n/src/RasterImage.cpp:2773 It's running out of memory in "mozilla::imagelib::RasterImage::AddSourceData" and it seems like it should be invoking the garbage collector at that point to free up some memory.
I've consolidated a number of bugs about image-heavy sites, including this one, into bug 660577. Please CC yourself on that bug if you want to follow along. Thanks.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 660577
You need to log in before you can comment on or make changes to this bug.