Open
Bug 1008646
Opened 10 years ago
Updated 2 years ago
"ABORT: Asked to discard but can't!"
Categories
(Core :: Graphics: ImageLib, defect)
Tracking
()
NEW
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: assertion, testcase)
Attachments
(2 files)
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.
Reporter | ||
Comment 1•10 years ago
|
||
Comment 2•10 years ago
|
||
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•10 years ago
|
||
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
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•