1008646 - "ABORT: Asked to discard but can't!"

Status: NEW

(Core :: Graphics: ImageLib, defect)

Description

[Jesse Ruderman]

Attachment: testcase

1. Create a profile with prefs.js:
     user_pref("image.mem.hard_limit_decoded_image_kb", 443);
2. Launch Firefox with the testcase on the command line
3. Click the button

###!!! ABORT: Asked to discard but can't!: 'force ? CanForciblyDiscard() : CanDiscard()', file image/src/RasterImage.cpp, line 1952

The exact limit seems to be important, so this bug might be fragile :/

The ability to have such a limit was added in bug 878577.

Comment 1

[Jesse Ruderman]

Attachment: stack

Comment 2

[Timothy Nikkel (:tnikkel)]

chrome images aren't forcibly discardable, so if we have enough chrome images to go over the hard limit we will hit this abort I guessing from a quick look.

The hard limit just doesn't handle such a situation.

Comment 3

[Shih-Chiang Chien [:schien] (UTC+8) (use ni? plz)]

The hard limit is introducing another possibility of fail to get current frame [1]. Should we use RequestDiscard() in RasterImage::GetCurrentImage() instead of ForceDiscard()?

[1] http://dxr.mozilla.org/mozilla-central/source/image/src/RasterImage.cpp?from=RasterImage.cpp&case=true#990