[Webkit-unassigned] [Bug 163298] New: [CG] Add the option to immediacy decode an image frame and control its memory caching

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Oct 11 14:28:19 PDT 2016


            Bug ID: 163298
           Summary: [CG] Add the option to immediacy decode an image frame
                    and control its memory caching
    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

This work is needed for asynchronous image decoding. By default an image frame is decoded only when it'e needed. Usually the image frame is needed when it is drawn. If the image decoding is done on the main thread, two things might happen. The main thread is blocked such that an activity, like scrolling, is not smooth. Secondly the image decoding is slow such that rendering a layout frame is done in more than 16ms, so we miss drawing a frame.

This bug should fix two things. It should add the option to immediately decode an image frame. This should happen on a different thread earlier than  the drawing time. The BitmapImage should also control when the image frame is deleted from memory. Currently CG can cache an image frame even if WebKit does not have a reference to it. The only way to guarantee an image frame is removed from memory is to delete the reference to the CGImageSourceRef.

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/20161011/dae7ea0c/attachment.html>

More information about the webkit-unassigned mailing list