Open
Bug 683284
(image-suck)
Opened 13 years ago
Updated 2 years ago
[meta] Images suck the snap out of Firefox (memory, flicker, decode/discard heuristics)
Categories
(Core :: Graphics: ImageLib, defect)
Core
Graphics: ImageLib
Tracking
()
NEW
People
(Reporter: jrmuizel, Unassigned)
References
(Depends on 5 open bugs)
Details
(Keywords: memory-footprint, meta, perf, Whiteboard: [please read comment 1 before adding dependencies][snappy:p2])
This is tracking bug for all of the imagey things we do worse at than other browsers.
Reporter | ||
Updated•13 years ago
|
Alias: image-suck
Updated•13 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Reporter | ||
Comment 1•13 years ago
|
||
I'd like this bug to only address bugs where our behaviour is a clearly wrong compared to other browsers. It's not clear from 124608 what the problem actually is.
No longer depends on: 124608
Blocks: 660577
Updated•13 years ago
|
No longer blocks: 685821
Whiteboard: [please read comment 1 before adding dependencies]
![]() |
||
Updated•13 years ago
|
Summary: We suck at images → [meta] We suck at images
Updated•13 years ago
|
![]() |
||
Updated•13 years ago
|
Whiteboard: [please read comment 1 before adding dependencies] → [please read comment 1 before adding dependencies][MemShrink:P1]
![]() |
||
Updated•13 years ago
|
Whiteboard: [please read comment 1 before adding dependencies][MemShrink:P1] → [please read comment 1 before adding dependencies]
Updated•13 years ago
|
Whiteboard: [please read comment 1 before adding dependencies] → [please read comment 1 before adding dependencies][snappy]
Comment 4•13 years ago
|
||
My Firefox crashes almost 20-30 times during a working day because of imagery memory consumption. I miss the good behaving Firefox before. I can hardly recall when is this happening, but it seems that 7.0 or 8.0 may be a start.
![]() |
||
Comment 5•13 years ago
|
||
> My Firefox crashes almost 20-30 times during a working day because of
> imagery memory consumption.
How do you know it's the memory for images that is the cause? The only changes to image memory handling that I'm aware of lately should have reduced the memory usage.
Comment 6•13 years ago
|
||
Thanks for your correction, and I do not know indeed if it's a consumption problem or not. But there is indeed problem in Firefox because other related bugs has direct me here.
(In reply to Robert Ciang from comment #4) > My Firefox crashes almost 20-30 times during a working day because of > imagery memory consumption. I miss the good behaving Firefox before. I can > hardly recall when is this happening, but it seems that 7.0 or 8.0 may be a > start. Not much change since 4.0 on image heavy site, the good old days your mention was 3.6. And 32bit Windows system is somehow worse, because an application can have only 2GB address space and Firefox will crash when it consumes about 1.5G RAM..
![]() |
||
Comment 8•13 years ago
|
||
I summarized this bug and its dependents in this email thread: https://groups.google.com/forum/#!topic/mozilla.dev.platform/9JZhTxGlG8k
Comment 9•13 years ago
|
||
> My Firefox crashes almost 20-30 times during a working day because of imagery memory consumption.
This is a metabug, for tracking multiple separate problems; it is not for discussing any one issue. If you have steps which reliably cause you to crash, please file a separate bug and CC me on it; I'll follow up.
Updated•13 years ago
|
Whiteboard: [please read comment 1 before adding dependencies][snappy] → [please read comment 1 before adding dependencies][snappy:p2]
Comment 11•13 years ago
|
||
Bug 659220 which was marked duplicate of bug 660577 which was marked duplicate of this raised a question that I don't see in the remaining live bugs on image consumption. Specifically that DOM/JS image objects are small, even though the images they are holding on to may be large. Since they are small they may not trigger a JS GC, leaving the image layer thinking those images are still in use.
Comment 15•12 years ago
|
||
This bug is related huge size about "images/content/used/uncompressed"? It can reproduce easily in flickr.com slideshow. Step 1. open this url in 3 more tabs. http://www.flickr.com/photos/myplanetexperience/7090845767/lightbox/ Step 2. click "play button" Step 3. 1 hour later, check about:memory It's a BIG problem in mobile or embedded linux environments. Thanks,
(In reply to HyungGon Baek from comment #15) > This bug is related huge size about "images/content/used/uncompressed"? > It can reproduce easily in flickr.com slideshow. > > Step 1. open this url in 3 more tabs. > http://www.flickr.com/photos/myplanetexperience/7090845767/lightbox/ > > Step 2. click "play button" > > Step 3. 1 hour later, check about:memory > > It's a BIG problem in mobile or embedded linux environments. > Thanks, That's roughly Bug 679775, and the fix is Bug 683290.
Comment 17•12 years ago
|
||
(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #16) > (In reply to HyungGon Baek from comment #15) > > This bug is related huge size about "images/content/used/uncompressed"? > > It can reproduce easily in flickr.com slideshow. > > > > Step 1. open this url in 3 more tabs. > > http://www.flickr.com/photos/myplanetexperience/7090845767/lightbox/ > > > > Step 2. click "play button" > > > > Step 3. 1 hour later, check about:memory > > > > It's a BIG problem in mobile or embedded linux environments. > > Thanks, > > That's roughly Bug 679775, and the fix is Bug 683290. Thank you very much. I've applied your patches on ff4.0 and I can't reporduce OOM freezing. Thanks!!!
![]() |
||
Comment 18•11 years ago
|
||
Wouldn't these qualify for blocking this bug too? https://bugzilla.mozilla.org/show_bug.cgi?id=941823 https://bugzilla.mozilla.org/show_bug.cgi?id=523950
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•