[Webkit-unassigned] [Bug 110355] Get rid of "non-composited contents" in CoordinatedLayerTreeHost

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=110355





--- Comment #7 from Jae Hyun Park <jae.park at company100.net>  2013-03-04 20:47:07 PST ---
(In reply to comment #5)
> (In reply to comment #4)
> > Currently, two CoordinatedTiles use the same UpdateAtlas in the same time. It is a bug that can crash in some platforms.
> > 
> > For example,
> > 1. m_nonCompositedContentLayer->flushCompositingStateForThisLayerOnly();
> > 2. CoordinatedTile::updateBackBuffer()
> > 3. FrameView::paintContents()
> > 4. FrameView::flushCompositingStateForThisFrame()
> > 5. CoordinatedGraphicsLayer::flushCompositingStateForThisLayerOnly()
> > 6. CoordinatedTile::updateBackBuffer()
> > 
> > #2 calls UpdateAtlas::beginPaint and #6 also calls UpdateAtlas::beginPaint before #2 is completed.
> > 
> > I think if this bug is resolved, above bug is also resolved.
> You can probably fix this one by changing CoordinatedLayerTreeHost to call 
>     bool didSync = m_webPage->corePage()->mainFrame()->view()->flushCompositingStateIncludingSubframes();
> before the other flushes.

The same problem still exists in iframe cases even if we call 
bool didSync = m_webPage->corePage()->mainFrame()->view()->flushCompositingStateIncludingSubframes(); 
before the other flushes.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.