[Webkit-unassigned] [Bug 226867] New: [MSE] When currentTime is a large value, it takes time to process SourceBufferPrivate::evictCodedFrames().

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jun 9 22:11:46 PDT 2021


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

            Bug ID: 226867
           Summary: [MSE] When currentTime is a large value, it takes time
                    to process SourceBufferPrivate::evictCodedFrames().
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Media
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: toshio.ogasawara at access-company.com

SourceBufferPrivate::evictCodedFrames() loops to evict frames in a unit of 30 seconds from MediaTime::zeroTime() to "currentTime - thirtySeconds".
In the case of that currentTime is very large (eg. 180,000,000), evictCodedFrames() loops huge times to complete the eviction process. (in the example, it loops 6,000,000 times.)
To make matters worse, the looping process is executed even if there is no MediaSample to be evicted in a track buffer.
That is a point which should be improved.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210610/86d28be3/attachment.htm>


More information about the webkit-unassigned mailing list