[Webkit-unassigned] [Bug 170408] New: Asynchronously decoded image frames should not be destroyed when switching encoded data buffers

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 3 11:38:10 PDT 2017


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

            Bug ID: 170408
           Summary: Asynchronously decoded image frames should not be
                    destroyed when switching encoded data buffers
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Images
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sabouhallawa at apple.com

When switching the encoded data buffers, it would be better if we could somehow tell the ImageDecoder to swap in the new contents without destroying anything. But right now the native ImageDecoder does not have a mechanism to do that so WebKit simply destroys all the decoded frames and then deletes the ImageDecoder itself. Then it sets the new data in the ImageSource which will recreate a new ImageDecoder.

For async image decoding, this aggressive flushing mechanism is not actually needed. The asynchronously decoded image frames are owned by WebKit. They are not referenced by the native ImageDecoder. Destroying them and re-decoding them again will generate exactly the same image frames. More importantly, destroying the decoded image frames, can cause flickering because the image can not be drawn till the second decode finish.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170403/47421dbf/attachment-0001.html>


More information about the webkit-unassigned mailing list