[Webkit-unassigned] [Bug 90375] Parallel image decoders
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Jul 18 18:55:55 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=90375
--- Comment #32 from Hin-Chung Lam <hclam at google.com> 2012-07-18 18:55:49 PST ---
> That depends on how we refactor RenderingLayerBacking. In this case, we retrieve a NativeImagePtr from RetainedModeBitmapImage. So we can't simply delegate the decision to GraphicsContext.
>
> I will let you know once we decide how we refactor RenderLayerBacking.
ah! That's right I forgot RenderLayerBacking. RenderLayerBacking does present an interesting case. In your code I understand now these two operations does actually trigger parallel decoding:
RetainedModeBitmapImage::currentFrameIsComplete() and
RetainedModeBitmapImage::nativeImageForCurrentFrame()
Without this extra type calling nativeImageForCurrentFrame() would cause a synchronous decoding for RenderLayerBacking.
Just a thought here, actually adding the notion of asynchronous decoding to BitmapImage, e.g.
BitmapImage::prepareCurrentFrameAsynchronouslyIfPossible()
BitmapImage::nativeImageForCurrentFrame(); // returns 0 if async frame requested but not ready
BitmapImage::currentFrameIsComplete(); // just a getter to see if current frame is ready
prepareCurrentFrameAsynchronouslyIfPossible() is similar to your retained mode counter but have it built-in to BitmapImage.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list