The problem of asking to setup web isolation is that it’s not that easy if we use 3rd party solution that do not support it yet. I’m currently under discussion with such vendor to ask them to support the CORP headers in their HTTP response but this may takes time.
The vendor is Datadog, for their RUM & Browser log components on web applications (but also probably for mobile SDK)
So to make it simple, the situation for us is:
- either we loose our monitoring on our application by setting the web isolation
- or we continue to have crap performances & bugs on the Zoom SDK (memory issues, video, shared screen)
To go back to this memory issue topic, activating the web isolation would enable us to continue to use the shared array buffer feature.
But currently the SDK is already using that feature, and we have memory issues. So… ?
The Zoom SDK is per definition relying on the CPU and the Memory. But definitely in the later version it’s using more and more memory. Looks like in term of Memory your doing the same logic as for the CPU : just use how much you can.
I probably simplify a bit, but that’s what we see. So the Zoom SDK definitely has some memory “issue” to work on it. It cannot rely on using more and more until it get kicked by the OS or the Web monitor for OOM reason.