Closed
Bug 1166981
Opened 10 years ago
Closed 9 years ago
Decode images in LIFO order
Categories
(Core :: Graphics: ImageLib, defect)
Core
Graphics: ImageLib
Tracking
()
RESOLVED
FIXED
mozilla41
Tracking | Status | |
---|---|---|
firefox41 | --- | fixed |
People
(Reporter: seth, Assigned: seth)
References
Details
Attachments
(1 file)
(deleted),
patch
|
tnikkel
:
review+
|
Details | Diff | Splinter Review |
We should decode images in LIFO order. See bug 1152147 and related bugs for more justification, but the basic idea is that images we've requested decoding for more recently are more likely to be visible. If we decode in FIFO order and we fall behind, we can easily needing to decode a bunch of images that, say, have scrolled way off screen, before we can decode images that are actually visible. We see this happen in practice frequently in e.g. the B2G Gallery app and on desktop Firefox when scrolling image-heavy pages.
Assignee | ||
Comment 1•10 years ago
|
||
Here's the patch. So easy!
Nicely, this also makes things a little more efficient by eliminating the pop
from the front of the array that we used in the FIFO scheduler.
Attachment #8608398 -
Flags: review?(tnikkel)
Updated•10 years ago
|
Attachment #8608398 -
Flags: review?(tnikkel) → review+
Assignee | ||
Comment 2•10 years ago
|
||
Thanks for the quick review!
This is pretty trivial but I think it might uncover some hidden timing assumptions in our tests, so I'm going for a full try job on this one.
Assignee | ||
Comment 3•10 years ago
|
||
Assignee | ||
Comment 4•10 years ago
|
||
Hmm. This mostly look OK, but there seem to be a lot of timeouts and test failures on B2G Desktop Linux x64 opt. I'm not sure what's going on there... I've retriggered a couple of jobs to investigate further.
Assignee | ||
Comment 5•10 years ago
|
||
Assignee | ||
Comment 6•10 years ago
|
||
Assignee | ||
Comment 7•9 years ago
|
||
Assignee | ||
Comment 8•9 years ago
|
||
Assignee | ||
Comment 9•9 years ago
|
||
Assignee | ||
Comment 10•9 years ago
|
||
Assignee | ||
Comment 11•9 years ago
|
||
I think we're now ready to go, based upon what I'm seeing on the newer try jobs. (Kevin told me there may really never have been a problem other than infrastructure issues, which may well be true, because I certainly can't reproduce those older failures locally.) Let's give this a shot.
Assignee | ||
Comment 12•9 years ago
|
||
Comment 13•9 years ago
|
||
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox41:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla41
You need to log in
before you can comment on or make changes to this bug.
Description
•