RESOLVED FIXED248585
currentTime progress even when playback has stalled 
https://bugs.webkit.org/show_bug.cgi?id=248585
Summary currentTime progress even when playback has stalled
Jean-Yves Avenard [:jya]
Reported 2022-11-30 22:22:57 PST
This problem got exposed in bug 236722. In bug 236722, playback doesn't actually start unless the entire media has been fetched. However, we can see that the progress bar is moving forward as if it did. It shouldn't. Somehow we are not detecting that the underlying playback framework has stalled and we fail to notify the content process which in turn will incorrectly estimate the currentTime.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2022-11-30 22:23:25 PST
<rdar://problem/102846199>
Jean-Yves Avenard [:jya]
Comment 2 2022-11-30 22:29:26 PST
actually, this has already been lodged. It got fixed but changes were reverted *** This bug has been marked as a duplicate of bug 230210 ***
Jean-Yves Avenard [:jya]
Comment 3 2022-12-02 15:13:40 PST
issue in bug 230210 can't be reproduced so let's start with a new bug
Jean-Yves Avenard [:jya]
Comment 4 2022-12-02 15:47:56 PST
Pull request: https://github.com/WebKit/WebKit/pull/7103
Jean-Yves Avenard [:jya]
Comment 5 2022-12-02 15:51:10 PST
problem can be seen when attempting to open the URL https://mediaserver.avenard.org/test/89041245.py?name=foo&stallOffset=100000&stallDuration=20&chunkSize=1024 , playback will not start until 20s after the first frame has been displayed
EWS
Comment 6 2022-12-06 02:23:45 PST
Committed 257403@main (384fb5b098b8): <https://commits.webkit.org/257403@main> Reviewed commits have been landed. Closing PR #7103 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.