We are currently trying to add functionality to these youtube-playback tests that would let us run them for a longer period of time. While working on this, I continuously receive the following error: "QuotaExceededError: The quota has been exceeded."
But what this Quota is related to is unclear. When I run this in Chrome, I see the following error, which is a bit more helpful:
```
msutil.js:92 Uncaught DOMException: Failed to execute 'appendBuffer' on 'SourceBuffer': The SourceBuffer is full, and cannot free space to append additional buffers.
at window.safeAppend (http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:92:8)
at loop (http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:589:12)
at http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:336:7
at http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:484:7
at window.FileSource.<anonymous> (http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:460:7)
at Request.onload (http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:274:10)
at XMLHttpRequest.<anonymous> (http://localhost/perf-youtube-playback/2019/harness/xhr.js:65:19)
```
To reproduce this issue, follow these instructions (there's probably a simpler way off getting this error to occur):
1. Clone https://github.com/mozilla/perf-youtube-playback.
1. Checkout this PR: https://github.com/mozilla/perf-youtube-playback/pull/4
1. Setup locally, following these instructions: https://github.com/mozilla/perf-youtube-playback/wiki#running-tests-locally
1. Once ready, navigate to: http://localhost/perf-youtube-playback/2019/main.html?test_type=playbackperf-test&muted=true&test_time=300
1. Click the test `22. PlaybackPerf.VP9.2160p60@1X`
1. Look for the QuotaExceededError in the console logging.
It would be great if the QuotaExceededError could be more informative about what the Quota refers to - in this case, that the SourceBuffer is full.
Also, I'm not sure if this is the correct component for this bug so feel free to change it if needed.
Bug 1580861 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We are currently trying to add functionality to these youtube-playback tests that would let us run them for a longer period of time. While working on this, I continuously receive the following error: `QuotaExceededError: The quota has been exceeded.`
But what this Quota is related to is unclear. When I run this in Chrome, I see the following error, which is a bit more helpful:
```
msutil.js:92 Uncaught DOMException: Failed to execute 'appendBuffer' on 'SourceBuffer': The SourceBuffer is full, and cannot free space to append additional buffers.
at window.safeAppend (http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:92:8)
at loop (http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:589:12)
at http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:336:7
at http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:484:7
at window.FileSource.<anonymous> (http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:460:7)
at Request.onload (http://localhost/perf-youtube-playback/2019/lib/mse/msutil.js:274:10)
at XMLHttpRequest.<anonymous> (http://localhost/perf-youtube-playback/2019/harness/xhr.js:65:19)
```
To reproduce this issue, follow these instructions (there's probably a simpler way off getting this error to occur):
1. Clone https://github.com/mozilla/perf-youtube-playback.
1. Checkout this PR: https://github.com/mozilla/perf-youtube-playback/pull/4
1. Setup locally, following these instructions: https://github.com/mozilla/perf-youtube-playback/wiki#running-tests-locally
1. Once ready, navigate to: http://localhost/perf-youtube-playback/2019/main.html?test_type=playbackperf-test&muted=true&test_time=300
1. Click the test `22. PlaybackPerf.VP9.2160p60@1X`
1. Look for the QuotaExceededError in the console logging.
It would be great if the QuotaExceededError could be more informative about what the Quota refers to - in this case, that the SourceBuffer is full.
Also, I'm not sure if this is the correct component for this bug so feel free to change it if needed.