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

Need to allow resource limitations to cause OperationError #2706

Open
alvestrand opened this issue Dec 14, 2021 · 0 comments
Open

Need to allow resource limitations to cause OperationError #2706

alvestrand opened this issue Dec 14, 2021 · 0 comments

Comments

@alvestrand
Copy link
Contributor

I had a situation today where we ran out of resources to create transceivers, resulting in an OOM situation.
This is a rather ugly way of signalling that the JS is doing something nonsensible. It would be nicer if we could throw an error when it's clear that the resource consumption is getting out of hand.

But the addTransceiver() steps currently allow for no such error.

Suggest adding a new step after step 7:

If the subsequent operation steps cannot be completed due to internal issues such as resource exhaustion, release all allocated resources and throw an OperationError.

Similar steps should probably be added to AddTrack too, and possibly even AddIceCandidate. The "Set a session description" function already has a catch-all error step (4.4.7).

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

1 participant