The canvas video occasionally freezes

Video SDK Type and Version
2.1.0

Description
The canvas video occasionally freezes. Stopping and re-rendering the video restores normal functionality.

This error occurred on a customer’s side, so we don’t have detailed logs. So, we can provide the session ID.

Thank you for your help!

Error?

1f52e22c-f1f6-4508-9368-d2767aef6b1d:1 Video Version:  2689
0a1c96f7-186d-4016-951f-5db74159cb92:1 Video Version:  2689
blob:https://econy.jp/5d2a4808-f852-44d1-b95f-519e03e5dd53:25726  not sharing decode type
Gs @ blob:https://econy.jp/5d2a4808-f852-44d1-b95f-519e03e5dd53:25726
(anonymous) @ blob:https://econy.jp/5d2a4808-f852-44d1-b95f-519e03e5dd53:24943
(anonymous) @ blob:https://econy.jp/5d2a4808-f852-44d1-b95f-519e03e5dd53:25060
blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:3237 cancelConsume interval 7 requestID null
blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:24013 videoShare.closeMedia
blob:https://econy.jp/5d2a4808-f852-44d1-b95f-519e03e5dd53:24013 videoShare.closeMedia
blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:5494  WebGL: INVALID_ENUM: activeTexture: texture unit out of range
u.cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:5494
cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:13092
cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:13408
cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:14903
c.cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:8722
(anonymous) @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:24019
(anonymous) @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:24018
(anonymous) @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:24025
blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:5498  WebGL: INVALID_ENUM: activeTexture: texture unit out of range
u.cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:5498
cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:13092
cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:13408
cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:14903
c.cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:8722
(anonymous) @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:24019
(anonymous) @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:24018
(anonymous) @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:24025
blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:5502  WebGL: INVALID_ENUM: activeTexture: texture unit out of range
u.cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:5502
cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:13092
cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:13408
cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:14903
c.cleanup @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:8722
(anonymous) @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:24019
(anonymous) @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:24018
(anonymous) @ blob:https://econy.jp/c3ee92c1-a80e-4689-b977-9e3ed2965e5b:24025
index.esm.js:20926  Uncaught (in promise) Error {stack: 'Error\n    at https://econy.jp/videosdk/index.esm.j…e (https://econy.jp/videosdk/index.esm.js:382:56)', name: 'EmptyError', message: 'no elements in sequence'}
m_ @ index.esm.js:20926
await in m_ (async)

How To Reproduce

  1. Users A and B join the meeting with their cameras on.
  2. Both users successfully start their cameras.
  3. After ~3.5 seconds, User A’s camera freezes, but User B can still see A’s video.
  4. When User A stops and restarts the camera, it displays normally.

3. Browser/client type and version
Browser: Edge version 119
OS: Window 11

No need for two users to join the meeting; sometimes, only one user has the same issue.

Hey @lmtruong1512

Thanks for your feedback.

So, we can provide the session ID.

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

Thanks
Vic

Hi @vic.yang,

Sorry, this error occurred on the customer’s side, and we don’t have detailed logs with session ID information. Could you help analyze the issue?

Thanks!

Hi @vic.yang ,
We’re encountering this issue again. Could you please take a look using the following session IDs: R3PCXwRmT+2RReSzzKASAg==, 8XLnIBWfShmEGvNK6Jv+yA==?

The problem occurs with a BOT user running on a headless browser. Here’s the relevant code snippet:

      const canvasElement = document.getElementById(ViewIdentifiers.PIN_CANVAS_VIEW);
      canvasElement.setAttribute('user-id', userId);
      await state.mediaStream.renderVideo(canvasElement, userId, canvasElement.width, 
            canvasElement.height, 0, 0, quality);

VideoSDK version: 2.1.0

Thanks in advance for your help!

Hi @lmtruong1512

Thanks for sharing the session IDs with us. We are working on investigating the issues.

Thanks
Vic

1 Like

Hi @vic.yang, Thank you for your continued support.

We want to follow up to see if there has been any progress on the investigation?

Hi @lmtruong1512

R3PCXwRmT+2RReSzzKASAg== , 8XLnIBWfShmEGvNK6Jv+yA==

After analyzing the logs, it seems that this issue might be related to the use of a Virtual Machine.

After receiving video for a period of time, it seems the VM fails to decode new video frames, resulting in video freeze.

We are continuing to analyze the issue further.

Thanks
Vic

1 Like

@vic.yang Thanks for the update and for looking into this.

Hi @vic.yang ,
Is there a permanent or temporary fix for this issue? If you find anything, please let me know. Thank you very much.

Hi @lmtruong1512

Is there a permanent or temporary fix for this issue?

Not at the moment. A fix may be available in the next version.

Thanks
Vic

1 Like

Hi @vic.yang ,
Is the “Virtual Machine” issue related to the Zoom SDK’s internal implementation, or is it dependent on the client-side environment?

Also, is there any way to mitigate or reduce the frequency of this bug on the client side while waiting for a fix in the upcoming version?

Hi @lmtruong1512

Is the “Virtual Machine” issue related to the Zoom SDK’s internal implementation, or is it dependent on the client-side environment?

It’s related to the virtual machine as well as our implementation — we’re actively working on fixing this issue.

is there any way to mitigate or reduce the frequency of this bug on the client side while waiting for a fix in the upcoming version?

Specifying video_webrtc_mode: 1 in the JWT explicitly enables WebRTC video, which can indeed help with video rendering on virtual machines that lack physical GPUs. However, in this mode, you’ll need to adjust your video rendering implementation:

Use attachVideo() instead of renderVideo() for rendering video.

Thanks
Vic

1 Like

This topic was automatically closed 25 hours after the last reply. New replies are no longer allowed.