Closed Bug 622475 Opened 14 years ago Closed 5 years ago

[NSFW - porn site] Fennec goes into OOM state and page loading is extremely slow in image site, followup 622397

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: romaxa, Unassigned)

References

()

Details

Attachments

(2 files)

It is impossible to load URL, because fennec images loading is extremely slow and memory greedy.

Hope timeless can provide URL to some stress page without porn content :)

On webkit this page loaded very fast and using only ~70-80Mb vs fennec (150 and more mb)
Interesting, I changed image.mem.decodeondraw -> true, and memory consumption still huge...
Depends on: 622536
With permissions.default.image = 2 (disabled images) - fennec consume for this page only ~30Mb, with disabled image placeholders pref it is ~20Mb 

Even with decodeondraw = true Fennec memory consumption on this page is huge on device it goes over 600Mb... 

Also more interesting is that Fennec process (Chrome) also consuming memory aline with content process, and at the end it drop memory back.. (~200Mb)
Need to check more why and where we allocating memory in content process
Interesting picture.... with decodeondraw enabled I got less CPU used by jpeg decoding and rest of CPU consumed by processing OnStatus/OnProgress messages... this looks really weird...
Backtrace for image surface allocation with decodeOnDraw enabled, joe is it expected to allocate memory which is not needed right now?
(In reply to comment #1)
> Interesting, I changed image.mem.decodeondraw -> true, and memory consumption
> still huge...

decode on draw only affects the behaviour of background tabs now. With decode on draw, we never decode images on background tabs (until you tab over to them); without decode on draw, we decode them as normal, but discard them if we don't tab over within a certain amount of time.
I did not get how to enable decode on draw... according to StoringSourceData, image.mem.discardable should be false and 
image.mem.decodeondraw also false

then we can get into http://mxr.mozilla.org/mozilla-central/source/modules/libpr0n/src/RasterImage.cpp#1181
Isn't this a duplicate of bug 608385?
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: