Bug 230443 - [MSE] SourceBufferWebMParser should ignore segment length
Summary: [MSE] SourceBufferWebMParser should ignore segment length
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Jean-Yves Avenard [:jya]
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2021-09-18 07:58 PDT by Jean-Yves Avenard [:jya]
Modified: 2023-09-20 03:08 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Yves Avenard [:jya] 2021-09-18 07:58:30 PDT 
STR:

- Load https://jyavenard.github.io/htmltests/tests/mse_webm/big.html
- this pages loads 5MB of webm at a time, until an exception occurs due to the source buffer throwing a QuotaExceededError

Results:
10801: SourceBuffer buffered ranges grew from TimeRanges: [0.007, 545.109) to TimeRanges: [0.007, 550.11)
10801: Loading buffer: [0, 888286)
10999: got error event
10999: ok(false) should not fire 'error' event
10999: SimpleTest.finish

Expected:
QuotaExceededError should be caught and it should display the maximum size of a source buffer.

When this happens, the video element throws a fatal error.

SourceBuffer QuotaExceededError shouldn't be a fatal error.
Comment 1 Radar WebKit Bug Importer 2021-09-18 07:58:50 PDT 
<rdar://problem/83271244>
Comment 2 Jean-Yves Avenard [:jya] 2021-09-20 06:31:19 PDT 
This issue occurs because the page keeps loading the content in a loop. The initial WebM Segment contains a set length.

libwebm errors when it sees content further than the initial segment length.

We should ignore that length as both Firefox and Chrome are doing.
Comment 3 Ahmad Saleem 2023-09-20 03:08:44 PDT 
@jya - Seems to load fine in STP178, is it fixed?