Closed Bug 739245 Opened 8 years ago Closed 4 years ago

On mobile, we should add resource limiting in the same way as iOS does for images

Categories

(Core :: ImageLib, defect)

x86_64
Linux
defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gw280, Unassigned)

References

(Blocks 1 open bug)

Details

iOS has known resource limits to stop the browser from using up huge amounts of memory being hogged by large image assets. The information from Apple is available here: http://developer.apple.com/library/safari/#documentation/AppleApplications/Reference/SafariWebContent/CreatingContentforSafarioniPhone/CreatingContentforSafarioniPhone.html#//apple_ref/doc/uid/TP40006482-SW15

We should do something similar on mobile.
This seems pretty reasonable to me, although note that these limits may have caused a bit of trouble when they released the iPad 3 (specifically, the jpeg sub-sampling):

http://duncandavidson.com/blog/2012/03/webkit_retina_bug
Bug #739245 states that an extra-large completely black animated png image with many frames will crash firefox on a non-mobile device, as well.
No longer blocks: 739159
Depends on: 1060869
This got implemented in bug 1060869, which moved all non-animated images into the SurfaceCache, which has a hard memory limit. Later bugs moved other image types (e.g. animated images) into the SurfaceCache. Any issues that remain should end up in a new bug.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.