Closed Bug 834437 Opened 11 years ago Closed 11 years ago

[layers-refactoring] Make layers refactor not regress android

Categories

(Core :: Graphics: Layers, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: jrmuizel, Assigned: jrmuizel)

References

Details

(Whiteboard: [metro-gfx])

      No description provided.
Whiteboard: [layers-refactor][metro-gfx]
Assignee: nobody → jmuizelaar
Summary: Make layers refactor not regress android → [layers-refactoring] Make layers refactor not regress android
Whiteboard: [layers-refactor][metro-gfx] → [metro-gfx]
So I think this mostly works. Some artefacts to hunt down, but I think we'll leave that until we finish more of the big things because they will only get regressed again, or if we're lucky fixed by accident.
Blocks: metro-omtc
I can repro the bad result in M8, but not that crash in M2. M1 and R2 look like webgl, which is busted for now. I'll try to fix M8 for now.
(In reply to Jeff Muizelaar [:jrmuizel] from comment #4)
> I fixed M8:
> https://tbpl.mozilla.org/?tree=Try&rev=c851f7919ff3

The R1 break is aa on mask layers. I have a lot of bitterness with such bugs. We haven't changed the mask layers code as far as I know, other than moving it, so I don't see how this could happen. Probably we should fuzz it.

The R3 fails look like a tile misloading or something. I'll look into that.

Worryingly, jrmuizel is still reporting flickering and rendering glitches. That R3 test seems to be the only evidence in our tests, that is a bit scary.
Blocks: 849261
No longer blocks: metro-omtc
Depends on: 851683
We have landed
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.