Open Bug 1849216 Opened 1 year ago Updated 1 month ago

Follow up on MSE buffered range mismatch

Categories

(Core :: Audio/Video: Playback, defect, P3)

defect

Tracking

()

People

(Reporter: alwu, Assigned: alwu)

References

(Depends on 5 open bugs)

Details

In bug 1846957, we discovered the buffered mismatching caught by diagnostic assertion, but we couldn't find out the culprit. So we change those assertion to debug-only, and will keep investigation on the root cause on this bug.

A code comment in DoEvictData() explains that data may contain zero duration frames. These would not show up in mBufferedRanges, so data is not necessarily empty if mBufferedRanges is empty. This would have led to the assertion failure in bug 1846957.

Depends on: 1909543
Depends on: 1906088
Depends on: 1909614
Depends on: 1909750
Depends on: 1916305
Depends on: 1911008
Depends on: 1914844
You need to log in before you can comment on or make changes to this bug.