Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOMException: "The quota has been exceeded." on Firefox only #258

Closed
Nodja opened this issue Oct 13, 2018 · 3 comments
Closed

DOMException: "The quota has been exceeded." on Firefox only #258

Nodja opened this issue Oct 13, 2018 · 3 comments

Comments

@Nodja
Copy link

Nodja commented Oct 13, 2018

Description

HLS video segments over a certain size (20MB?) cause a DOMException: "The quota has been exceeded." to occur on Firefox. Works fine on chrome and edge.

Steps to reproduce

Explain in detail the exact steps necessary to reproduce the issue.

  1. Load https://jsbin.com/cekitaxace/edit?html,output

Results

Expected

Video should play

Error output

VIDEOJS: ERROR: (CODE:-3 undefined) The quota has been exceeded. Object { code: -3, type: "APPEND_BUFFER_ERR", message: "The quota has been exceeded.", originalError: DOMException } video.js:128:5

Additional Information

videojs-http-streaming version

1.3.0

videojs version

video.js 7.2.3

Browsers

  • Firefox 62.0.3

Platforms

  • Windows 10
@welcome
Copy link

welcome bot commented Oct 13, 2018

👋 Thanks for opening your first issue here! 👋

If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
To help make it easier for us to investigate your issue, please follow the contributing guidelines.

@Nodja
Copy link
Author

Nodja commented Oct 13, 2018

I just want to be known that I'm using Sintel with an increased time per segment for demonstration purposes. I ran into the bug in a real scenario that used ~35000kbps segments, but the content is copyrighted so I cannot post it here.

@forbesjo
Copy link
Contributor

This looks similar to #192, we're working on a fix for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants