Closed Bug 1197972 Opened 9 years ago Closed 9 years ago

native-theme/492155-3.html fails with assertions on Linux debug reftests when APZ is enabled

Categories

(Core :: Panning and Zooming, defect)

Unspecified
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1204824

People

(Reporter: kats, Assigned: kats)

References

Details

The test at layout/reftests/native-theme/492155-3.html seems to be consistently failing on Linux debug R-e10s suites when APZ is enabled. This will need investigation/fixing.
According to a recent try push I did the assertion that is firing is:

19:48:16 INFO - [Parent 1970] ###!!! ASSERTION: Non preserves axis aligned transform with clipped child should have forced intermediate surface: 'is2D && matrix.PreservesAxisAlignedRectangles()', file /builds/slave/try-lx-d-000000000000000000000/build/src/gfx/layers/Layers.cpp, line 718 19:48:16 INFO - #01: mozilla::layers::Layer::CalculateScissorRect(mozilla::gfx::IntRectTyped<mozilla::RenderTargetPixel> const&) [gfx/layers/Layers.cpp:717] 19:48:16 INFO - #02: void mozilla::layers::ContainerPrepare
I can reproduce this locally. The is2D check is true, but the matrix looks like this (at least on the iteration I just did):

(gdb) p matrix
$3 = {
  _11 = 0.866025448,
  _12 = 0.5,
  _21 = 0,
  _22 = 1.15470052,
  _31 = 58,
  _32 = -7.73503113
}
I'm pretty sure this test wasn't failing before so I'm going to try and bisect to see when it started failing. Hopefully that will shed some more light on what's going on.
Assignee: nobody → bugmail.mozilla
Actually it looks like it's been happening for at least a couple of months so I aborted my bisection - even if it does find something it wouldn't be that useful.
The patch on bug 1204824 seems to fix this for me locally.
Depends on: 1204824
APZ-enabled try push at https://treeherder.mozilla.org/#/jobs?repo=try&revision=41a2e496ef4b&group_state=expanded no longer has this failing. \o/
Status: NEW → RESOLVED
Closed: 9 years ago
No longer depends on: 1204824
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.