Zoom Web Video SDK – Video not starting in Edge InPrivate mode (Error code 205: low memory)

Video SDK Web
1

Description
When joining a session using the Zoom Video SDK for Web, I cannot see other participants’ videos and I also cannot start my own video.
The browser console shows an error message indicating low memory (code: 205).
However, checking the Windows Task Manager shows that there is still available system memory.

Browser Console Error
'Uh-oh! You’re running low on memory. Please close all browsers and rejoin the meeting.
type: video
code: 205

Which Web Video SDK version?
2.2.5

To Reproduce(If applicable)
Steps to reproduce the behavior:

  1. Join Meeting

Screenshots

image

image
image887×496 83.8 KB

Troubleshooting Routes

  • Attempted refreshing the meeting webpage (F5) while in the session, but the issue persisted.

Device (please complete the following information):

  • Device: Dell
  • OS: Windows 11 Pro
  • Browser:Edge
  • Browser Version: 119.0.2151.97 (Official Build) (32-bit) (Chromium-based)

Additional context
On the same PC, joined the meeting as two separate users:

  • User A: Joined using Microsoft Edge in normal browsing mode → Worked normally, no issues encountered.

  • User B: Joined using Microsoft Edge in InPrivate mode → Encountered the issue described in the “Browser Console Error” section.

2

Hi @Anh_Duc Are you able to repliate this error with our sample app?

3

Hey @Anh_Duc

Thanks for your feedback.

Could you share some problematic session IDs with us for troubleshooting purposes?

Thanks
Vic

4

hi @vic.yang @ticorrian.heard , thanks for your support!

Here is the meeting ID and the related session IDs for your reference:

  • Meeting ID: 0131680807_1755228013189

  • Session IDs:

    • pq2OMDJTQeSgAwNs7eVsZw==
    • jKAHzoiBStC6ytrOh+eAFw==
    • p1AsuP0eQ7SAkU77UjEkpg==

Here are the user details involved:

  • User ID: f7544a38-1031-7011-1503-dfd3346489f2
    • Username: duc2 — the user who encountered the issue

Thank you again for your support. Please let me know if you need any additional information for troubleshooting.

5

Hi @Thong1

  • pq2OMDJTQeSgAwNs7eVsZw==

This session shows the error ActiveMediaFailedCode.VideoStreamEnded = 202, which may be because the camera was interrupted by another program using it, causing the video stream to end.

  • jKAHzoiBStC6ytrOh+eAFw==

There’s no obvious error, but the user joined with a device that doesn’t have a GPU, which may cause the virtual background to be unavailable.

  • p1AsuP0eQ7SAkU77UjEkpg==

This is indeed a low memory issue, and we are currently investigating it.

Thanks
Vic

1 Like
6

Hi @vic.yang

Thank you for your support and detailed feedback.
I hope the team can soon identify the root cause related to the low memory issue.

Thanks again!

7

Hi @Thong1

  • p1AsuP0eQ7SAkU77UjEkpg==

We found that this may be because Edge on the device is a 32-bit application rather than the mainstream 64-bit version.

This is a known issue on 32-bit Chrome or Edge. In theory, up to 2048MB of memory can be allocated for the application, but testing shows that only about 240MB can actually be allocated. This causes the Video and Share features to fail with OOM errors during pre-allocation of memory.

We will make some optimizations for 32-bit Chrome/Edge in future versions, but we still recommend that users use the 64-bit application.

Thanks
Vic

1 Like
8

Hi @vic.yang

Thank you for your detailed explanation and recommendation. I understand that the issue is related to the 32-bit version of Chrome/Edge and the memory limitation it imposes.

In fact, this issue is quite rare on our side since most of our users are already using the 64-bit version. However, besides switching to 64-bit, may I ask if there are any other possible workarounds or temporary solutions to mitigate this issue?

Thanks again for your support.

Best regards,
Thong

9

Hi @Thong1

if there are any other possible workarounds or temporary solutions to mitigate this issue?

If you don’t use the screen share feature, you can be recommended to use WebRTC video on a 32-bit application by specifying video_webrtc_mode in the JWT. However, there isn’t currently a complete way to detect whether the application is 32-bit.

Thanks
Vic