Open Bug 1282209 Opened 5 years ago Updated 3 years ago

We should run imgFrame::Optimize off-main-thread

Categories

(Core :: ImageLib, defect, P3)

defect

Tracking

()

People

(Reporter: seth, Assigned: seth)

Details

(Keywords: feature, Whiteboard: [gfx-noted])

There are two reasons why we need to start running imgFrame::Optimize off-main-thread:

(1) Doing more work off-main-thread is good.

(2) Because we have to do it on-main-thread, we can't wait for it when we need to draw, which means that when there are rendering differences between the optimized and non-optimized version of the image (and there frequently are), we have to mark massive numbers of tests fuzzy, because whether we end up with the optimized or unoptimized version is a race. Indeed, this has already happened. See bug 1128229 for an example.

It's unclear to me, after poking around in the Moz2D code that gets called (which is where the problems, if any, would lie) whether this is even difficult at this point. Let's get it figured out.
Keywords: feature
Whiteboard: [gfx-noted]
You need to log in before you can comment on or make changes to this bug.