Summary: | REGRESSION (r166860): ASSERTION FAILED: !isCalculated() on fast/css/image-set-value-not-removed-crash.html | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> | ||||
Component: | CSS | Assignee: | Darin Adler <darin> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | bfulgham, commit-queue, darin, esprehn+autocc, glenn, gyuyoung.kim, kling, macpherson, menard, rniwa | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
Alexey Proskuryakov
2014-04-09 23:37:04 PDT
Skipped the test in debug builds in <http://trac.webkit.org/r167070>. What’s new here is the assertion. The bug isn’t new. I’ll fix this. I wonder why it’s *almost* every time instead of every time. It’s bizarre; this test case does not involve calculated values. I wonder how a calculated value gets in there. FWIW, it's reproducible for me locally. Looking at the flakiness dashboard results more closely, I think that it's actually every time - some of the runs are shown as timeouts, but I'm pretty certain that it's a tools bug, and we just fail to detect a crash that happened. The calculation here is created as part of animation. We are animating from the value 26829% to the value 2, so during the animation the current value of the property is a combination of both. The CSSComputedStyle code doesn’t know how to serialize something that is neither a percentage nor a number. I imagine there are a lot more cases like this in computed style. Because the code depends on the timing of the animation, I imagine it won’t always crash the same way every time. Created attachment 229209 [details]
Patch
Comment on attachment 229209 [details]
Patch
r=me, but you should also unskip the test.
Committed r167192: <http://trac.webkit.org/changeset/167192> Part of the fix for CVE-2014-4410. |