Hello, we’re facing an issue with the participant inside a meeting that’s viewing a share screen from other participant, the viewer is receiving and OPERATION_TIMEOUT error and the screen share space is being blank all the time. That only happens with just one specific person sharing and only happens when that person shares a specific apps’ window.
This session happened today and the same sharer I detailed in the opening of this ticket was the host today and tried to share a Figma’s window installed in his MacOS.
We analyzed the session log and found that the host sent the sharing content with a resolution exceeding 4K. The receiving end could not decode and render this content without SharedArrayBuffer enabled.
Workarounds for the issue are:
Enable the SharedArrayBuffer if possible.
Or adjust the size of the application that is being shared.
At today’s meeting (vQK50nPDT42qSGMQQyHy4w==) the host tried a different thing.
He putted the Figma app window over the 4K monitor and started sharing it, and it worked for everybody. While sharing he moved the window to over his 5K x 2K monitor (the one that doesn’t work when the Figma app windows is over there and he tries to share) and it continued to work as expected.
Thanks for sharing more information about this issue.
vQK50nPDT42qSGMQQyHy4w==
We analyzed the log and found that the content size on the second monitor, referred to as the 5K x 2K monitor, is smaller than it was in the previous session (ZBaKx994Q2umFf9GuhTYew==). The screen capture was done within the browser, which may have applied some optimizations, or the application window size might be smaller compared to the previous session.
On the second option, is there a way to detect the size of the windows the user is sharing so we can warning him to reduce the size of it ?
I checked in the SDK reference and didn’t found. But would like to double check with you.
And just to make sure, Zoom’s SDK don’t have a third option so we can share those big windows without the SharedArrayBuffer on ?