ASSERTION FAILED: length.isCalculated()
https://bugs.webkit.org/show_bug.cgi?id=187093
Summary ASSERTION FAILED: length.isCalculated()
Frédéric Wang (:fredw)
Reported 2018-06-27 06:10:02 PDT
ASSERTION FAILED: length.isCalculated() ../../Source/WebCore/css/CSSComputedStyleDeclaration.cpp(502) : WTF::Ref<WebCore::CSSPrimitiveValue> WebCore::valueForImageSliceSide(const WebCore::Length&) This is triggered by the following testcase: https://w3c-test.org/infrastructure/assumptions/html-elements.html more specifically, the tests "CSS div/span definitions (only valid if pre-reqs pass)".
Attachments
Ryan Haddad
Comment 1 2018-07-06 16:13:34 PDT
*** Bug 187421 has been marked as a duplicate of this bug. ***
Ryan Haddad
Comment 2 2018-07-06 16:41:17 PDT
Since it was consistently crashing, I went ahead and skipped this test on debug in https://trac.webkit.org/r233603
Alexey Shvayka
Comment 3 2020-03-17 01:53:14 PDT
Also triggered by https://w3c-test.org/css/css-cascade/all-prop-initial-xml.html: ASSERTION FAILED: length.isCalculated() ./css/CSSComputedStyleDeclaration.cpp(117) : Ref<WebCore::CSSPrimitiveValue> WebCore::valueForImageSliceSide(const WebCore::Length &) 1 0x304adcc59 WTFCrash 2 0x2e80074cb WTFCrashWithInfo(int, char const*, char const*, int) 3 0x2ea5de09c WebCore::valueForImageSliceSide(WebCore::Length const&) 4 0x2ea5c7b52 WebCore::valueForNinePieceImageSlice(WebCore::NinePieceImage const&) 5 0x2ea5ba52a WebCore::ComputedStyleExtractor::valueForPropertyInStyle(WebCore::RenderStyle const&, WebCore::CSSPropertyID, WebCore::RenderElement*) 6 0x2ea5b1cc5 WebCore::ComputedStyleExtractor::propertyValue(WebCore::CSSPropertyID, WebCore::EUpdateLayout) 7 0x2ea5b1a05 WebCore::CSSComputedStyleDeclaration::getPropertyCSSValue(WebCore::CSSPropertyID, WebCore::EUpdateLayout) const 8 0x2ea5cc760 WebCore::CSSComputedStyleDeclaration::getPropertyCSSValueInternal(WebCore::CSSPropertyID) 9 0x2ea6a7c95 WebCore::CSSStyleDeclaration::namedItem(WTF::AtomString const&)
Radar WebKit Bug Importer
Comment 4 2020-06-26 08:31:18 PDT
Note You need to log in before you can comment on or make changes to this bug.