https://crash-stats.mozilla.com/report/index/6cbd9a0d-694d-4ccc-ac72-a92860170817 Seen while looking at crash stats: http://bit.ly/2uUqWp6. Crashes first started using 20170815100349. 13 crashes/8 installs, all Windows 10. Possible regression range based on Build ID: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=564e82f0f289af976da01c2d50507017bbc152b5&tochange=6ebc251bd288c268b020815025b05854ccde5c08
Some URLs: http://fiddle.jshell.net/_display/ https://www.reddit.com/r/hardware/ http://browserbench.org/Speedometer/ Moz Crash Reason: MOZ_RELEASE_ASSERT(mOutstandingAsyncPaints == 0)
Severity: normal → critical
Crash Signature: [@ mozilla::layers::CompositorBridgeChild::NotifyFinishedAsyncPaintTransaction ]
I suspect one of you guys will know what this is supposed to do and why it might go wrong! This seems like it may be related to advanced layers? Although that landed in early July so doesn't really match when the crashes started.
It's OMTP related, dvander (or Mason) will probably understand it!
10 months ago
Priority: -- → P3
7 months ago
This was probably fixed a long time ago but CC'ing Ryan just in case.
You need to log in before you can comment on or make changes to this bug.