Thanks for testing that out on 1.9.6, I’m glad to hear that you’re seeing the update addressed the audio issues that you were having.
When it comes to RAM allocation, this can vary greatly based on the OS that you’re running the browser on. Further, RAM allocation by itself isn’t always bad and can often by a performance optimization done by a developer or automatically by a compiler/interpreter.
Zoom scales its consumption based on the resources available. If there is a compute or network constraint, you’ll see that Zoom will do its best to adjust to this limitation. This means that if there is an excess of a resources, Zoom will also attempt to scale quality up as much as possible.
Considering that our Web SDK follows the same system requirements as our Web Client (4GB RAM recommended), 2-3 GB RAM doesn’t seem too far outside what you can expect with the Web Client or Web SDK.
If you or @nvivot would like this investigated further, please create a new topic including information on the OS you’re using and the RAM usage that you’re seeing. I’ll follow up with you there and engage our engineering team if necessary.