- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Dec 2021 13:35:36 +0000
- To: public-webrtc@w3.org
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc: == Need to allow resource limitations to cause OperationError == 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). Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2706 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 December 2021 13:35:37 UTC