Failed to construct 'AudioContext': number of hardware contexts reached maximum

[joggienl]

Failed to construct 'AudioContext': number of hardware contexts reached maximum

[Lehren]

First of all audioContext.close() returns a Promise. So setting the recorder to null and all subsequent actions will have to be done asynchronously.

Second of all why is it neccesary to close the resource? By unmounting and mounting you mean to stop the recording of audio, do some things (like changing the page) and resuming the audio recording?
In which case audioContext.suspend() and audioContext.resume() work just fine. They too return Promises.

[joggienl]

First of all audioContext.close() returns a Promise. So setting the recorder to null and all subsequent actions will have to be done asynchronously.

I think you refer to the code example, I did notice it returns a promise. I was just demonstrating things could be done. In practice you would indeed put it in the promise or use async/await.

Second of all why is it neccesary to close the resource?

Because not closing results in error messages when you set AudioRecorder to null. Especially if you have an single-page-application. Hardware resources are still claimed to be in use (e.g. they are not freed up). The close function should free that resources. Note that Edge has Garbage Collection that does free up the resource by default (other browsers don't).

By unmounting and mounting you mean to stop the recording of audio, do some things (like changing the page) and resuming the audio recording?
In which case audioContext.suspend() and audioContext.resume() work just fine. They too return Promises.

I meant mount/un-mounting of a React component. These are stateless in simple form and proper cleanup of resources becomes important this way. Also due to the single-page-application that most React apps use.

From consumer point of view (the react app) I don't want to call audioContext features at all. If, for example, the SDK would manage a singleton instance or something like that for the audioContext and does a suspend/resume: would be fine.

Nevertheless I think it would be great to have a kind of cleanup function for the recorder.

[joggienl]

closing this one because I think it is not relevant atm.