Created attachment 319440 [details] Backtrace Crash in WebCore::Length::isCalculatedEqual: Truncated backtrace: Thread no. 1 (10 frames) #0 WebCore::operator== at /usr/src/debug/webkitgtk-2.16.1/Source/WebCore/platform/CalculationValue.h:160 #1 WebCore::Length::isCalculatedEqual at /usr/src/debug/webkitgtk-2.16.1/Source/WebCore/platform/Length.cpp:284 #2 WebCore::Length::operator== at /usr/src/debug/webkitgtk-2.16.1/Source/WebCore/platform/Length.h:226 #3 WebCore::TranslateTransformOperation::operator== at /usr/src/debug/webkitgtk-2.16.1/Source/WebCore/platform/graphics/transforms/TranslateTransformOperation.cpp:35 #4 WebCore::TransformOperation::operator!= at /usr/src/debug/webkitgtk-2.16.1/Source/WebCore/platform/graphics/transforms/TransformOperation.h:60 #5 WebCore::TransformOperations::operator== at /usr/src/debug/webkitgtk-2.16.1/Source/WebCore/platform/graphics/transforms/TransformOperations.cpp:45 #6 WebCore::StyleTransformData::operator== at /usr/src/debug/webkitgtk-2.16.1/Source/WebCore/rendering/style/StyleTransformData.cpp:53 #7 WebCore::DataRef<WebCore::StyleTransformData>::operator== at /usr/src/debug/webkitgtk-2.16.1/Source/WebCore/rendering/style/DataRef.h:82 #8 WebCore::StyleRareNonInheritedData::operator== at /usr/src/debug/webkitgtk-2.16.1/Source/WebCore/rendering/style/StyleRareNonInheritedData.cpp:233 #9 WebCore::DataRef<WebCore::StyleRareNonInheritedData>::operator== at /usr/src/debug/webkitgtk-2.16.1/Source/WebCore/rendering/style/DataRef.h:82 I have only one report of this total, so it's probably low priority. Better backtrace attached.
Maybe it's caused by https://bugs.webkit.org/show_bug.cgi?id=179675, though may backtrace is totally different
<rdar://problem/35536485>
Is this a crash or assertion?
Attached backtrace is from release version where asserts are disabled, and Length::calculationValue() doesn't have RELEASE_ASSERT. So it's not enough to state that these two issues are same
Need to test to see if this still occurs.
I'm pretty sure this is a duplicate of bug 237389, so I'm closing this. We can reopen if we see these kind of crashes again. *** This bug has been marked as a duplicate of bug 237389 ***