RESOLVED DUPLICATE of bug 164381 164774
Crash in WebCore::SVGRenderSupport::updateMaskedAncestorShouldIsolateBlending 
https://bugs.webkit.org/show_bug.cgi?id=164774
Summary Crash in WebCore::SVGRenderSupport::updateMaskedAncestorShouldIsolateBlending
Dieter Komendera
Reported 2016-11-15 08:22:57 PST
Created attachment 294836 [details] crash log I can reliably reproduce the crash with these steps: 1) Go go https://www.theguardian.com/world/2016/nov/15/japan-fixes-vast-fukuoka-city-sinkhole-repaired-two-days 2) Scroll down towards the "related content" section macOS 10.12.1 (16B2555) Release 17 (Safari 10.1, WebKit 12603.1.11.1) Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.WebCore 0x000000010cb8844b WebCore::SVGRenderSupport::updateMaskedAncestorShouldIsolateBlending(WebCore::RenderElement const&) + 123 1 com.apple.WebCore 0x000000010cadcdda WebCore::RenderElement::styleDidChange(WebCore::StyleDifference, WebCore::RenderStyle const*) + 122 2 com.apple.WebCore 0x000000010be22e1d WebCore::RenderSVGModelObject::styleDidChange(WebCore::StyleDifference, WebCore::RenderStyle const*) + 77 3 com.apple.WebCore 0x000000010cbc74fa WebCore::RenderTreeUpdater::createRenderer(WebCore::Element&, WebCore::RenderStyle&&) + 778 4 com.apple.WebCore 0x000000010cbc652d WebCore::RenderTreeUpdater::updateElementRenderer(WebCore::Element&, WebCore::Style::ElementUpdate&) + 349 5 com.apple.WebCore 0x000000010cbc5700 WebCore::RenderTreeUpdater::updateRenderTree(WebCore::ContainerNode&) + 592 6 com.apple.WebCore 0x000000010cbc543b WebCore::RenderTreeUpdater::commit(std::__1::unique_ptr<WebCore::Style::Update, std::__1::default_delete<WebCore::Style::Update> >) + 411 7 com.apple.WebCore 0x000000010c193a8e WebCore::Document::recalcStyle(WebCore::Style::Change) + 766 8 com.apple.WebCore 0x000000010bd824d6 WebCore::Document::updateLayout() + 134
Attachments
crash log (105.92 KB, text/plain)
2016-11-15 08:22 PST, Dieter Komendera 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2016-11-16 15:02:37 PST
This bug should be fixed in the Safari Technology Preview Release 18 that was posted today. *** This bug has been marked as a duplicate of bug 164381 ***
Note You need to log in before you can comment on or make changes to this bug.