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

Status: RESOLVED WORKSFORME

(Core :: Graphics: ImageLib, defect)

Description

[George Wright (:gw280) (needinfo me!)]

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.

Comment 1

[Justin Lebar (not reading bugmail)]

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

Comment 2

[Gunter Königsmann]

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.

Comment 3

[Seth Fowler [:seth] [:s2h]]

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.