[Webkit-unassigned] [Bug 167618] New: The current frame of an image should not deleted if another frame is asynchronously being decoded

[bugzilla-daemon at webkit.org]

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

            Bug ID: 167618
           Summary: The current frame of an image should not deleted if
                    another frame is asynchronously being decoded
    Classification: Unclassified
           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

Decoding multiple frames from the same image is not thread-safe. Since the next frame may not be ready at the time BitmapImage::draw() is called, the current frame has to be drawn. If the current frame is not available, drawing the current frame will invoke the image decoding from the drawing commit thread. This may lead to a crash when two threads update the image decoded frames data at the same time.

-- 
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/20170131/68e80188/attachment-0001.html>