197731 2019-05-08 21:11:49 -0700 Sometimes we hit ASSERT(!parentClipRect.isInfinite()) in RenderLayerBacking::computeParentGraphicsLayerRect 2019-05-08 21:24:14 -0700 1 1 1 Unclassified WebKit Compositing WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 197695 https://bugs.webkit.org/show_bug.cgi?id=126160 P2 Normal --- 1 simon.fraser webkit-unassigned simon.fraser zalan oldest_to_newest 1534625 0 simon.fraser 2019-05-08 21:11:49 -0700 At webkit r245059, we sometimes assert at ASSERT(!parentClipRect.isInfinite()) in RenderLayerBacking::computeParentGraphicsLayerRect. I can reproduce this in DumpRenderTree with accessibility/media-element.html 1534627 1 simon.fraser 2019-05-08 21:13:46 -0700 This code runs when we have a m_ancestorClippingLayer, and we make one based on the result of RenderLayerCompositor::clippedByAncestor(), which uses: layer.backgroundClipRect(RenderLayer::ClipRectsContext(computeClipRoot, TemporaryClipRects)).isInfinite() However, RenderLayerBacking::computeParentGraphicsLayerRect() is doing: ShouldRespectOverflowClip shouldRespectOverflowClip = compositedAncestor->isolatesCompositedBlending() ? RespectOverflowClip : IgnoreOverflowClip; RenderLayer::ClipRectsContext clipRectsContext(compositedAncestor, TemporaryClipRects, IgnoreOverlayScrollbarSize, shouldRespectOverflowClip); LayoutRect parentClipRect = m_owningLayer.backgroundClipRect(clipRectsContext).rect(); // FIXME: Incorrect for CSS regions. so 'shouldRespectOverflowClip' differs. 1534632 2 simon.fraser 2019-05-08 21:21:06 -0700 That code came from https://trac.webkit.org/changeset/168314/webkit 1534636 3 simon.fraser 2019-05-08 21:24:14 -0700 *** This bug has been marked as a duplicate of bug 197695 ***