New issue
Advanced search Search tips

Issue 907268 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 906373



Sign in to add a comment

See if we can cap MSE MP4 trun sequences with lots of sample_size==0

Project Member Reported by wolenetz@chromium.org, Nov 20

Issue description

One common route to MSE fuzzer timeout is a fuzzed trun containing a large sample_count, all with sample_size=0 (typically via trex default_sample_size == 0 and trun tr_flags' sample-size-present flag not set).

We could arbitrarily cap or reject such sequences in our parser, though I'm averse to doing that unless usage data indicates such sequences are rare in real content for our users.

This bug tracks adding instrumentation to determine if such capping/rejection wouldn't impair actual user experience (while letting the fuzzers operate more efficiently).
 
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment