Issue metadata
Sign in to add a comment
|
3d Animation freezes compositor |
||||||||||||||||||||||||
Issue descriptionon tip of tree only stable works only repro'd on linux other platforms may or may not be affected steps: load attached file, notice animation stops after 1/10 to 8 seconds. expected: animation continues to 100s This is a sub case of bug 626095 The key thing that stops it is an animation around a particular value of a 3d transform for a polygon that doesn't actually render anything. Even on a build with logging added to the 3d sorting/handling code it isn't getting any output. Once stopped the tab does not produce any more output, even though devtools reports the positon of main thread animations continues to change, and even when the page is reloaded. I notice in ,gpu traces that swap buffer calls seem to have stopped. I haven't bisected across versions.
,
Dec 2 2016
Manual bisect points at this: commit 8c14bf7d37bec879a5caa162f2c72a303da1a6e0 Date: Wed Oct 5 12:10:31 2016 -0700
,
Dec 2 2016
That's...unfortunate. That means that this was previously depending on undefined overflow behavior somewhere in the pipeline. I don't understand why frames aren't continuing to be pumped, though.
,
Dec 2 2016
Oh bother, this is in earlier releases than I knew Validated it freezes a pixel 1 on ChromeOS 56
,
Dec 5 2016
M55 - stable channel release exhibits this freeze in both the test and and in the wild. (626095)
,
Dec 9 2016
The compositor is starting impl frames as usual, but draws are earlying out because of no damage. So somewhere in the damage rect computation the clamping of overflow must be causing a previously non-empty rect to become empty.
,
Dec 12 2016
,
Jan 19 2017
This P1 hang seems to have dropped of the radar? Assigning to enne@ per #2. This seems still reproducible as of 57.0.2985.0.
,
Jan 19 2017
If I hack cc::DamageTracker to always have a damage rect of gfx::Rect(0,0,10000,10000) then this runs fine. I think this is a duplicate of issue 678432 . |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by petermayo@chromium.org
, Dec 2 2016