`stream.startVideo` freezed on Edge and throw error

Video SDK Web
1

Description

  • On some machines using the Edge browser, starting a video stream fails intermittently.
  • Calling stream.startVideo() sometimes freezes for a long time before throwing an error, and in some cases, it remains frozen indefinitely.
    (Other browsers work fine)

After an extended period, some devices throw the following error:

Uncaught TypeError: Cannot read properties of null (reading 'Set_WaterMark_Info')
    at f836a31f-95dd-4ee7-84c2-a8b983ef9ffc:24375:20

Some throw this error:

name: 'Empty error',  message: 'no elements in sequence'

As a result, when attempting to render the video, the following error occurs:

Uncaught (in promise) {"type":"INVALID_PARAMETERS","reason":"user is not sending video"}

This is my sessionId: Ob4FtMyHTlC8qMpHZFYSiA==

I would appreciate any help.

Browser Console Error

Which Web Video SDK version?
VideoSDK: 2.1.0

Video SDK Code Snippets

    try {
      let videoOptions = {
        cameraId: cameraId,
        hd: state.mediaStream.isSupportHDVideo(),
        originalRatio: window.isMobile
      };

      if (state.mediaStream.isSupportVirtualBackground() && virtualBackground) {
        videoOptions.virtualBackground = { imageUrl: virtualBackground };
      }
      await state.mediaStream.startVideo(videoOptions);
    } catch (error) {
      Logger.error('[VIDEO-SDK JS] startVideoStream error', error);
      throw error;
    }

To Reproduce(If applicable)

  1. User A turn on camera and join meeting
  2. User B use edge turn on camera and join meeting
  3. When enter meeting → use B can’t start video and throw error as above

Device (please complete the following information):

  • Device: Window 10
  • Browser: Edge
  • Browser Version: Edge version 119, 131
1 Like
2

Hey @lmtruong1512

Thanks for your feedback.

We are working on investigating this issue and will keep you updated.

Thanks
Vic

2 Likes
3

@vic.yang
Thank you very much! If you have any useful information or a temporary workaround, please let me know—we urgently need this fix.

4

Hey @lmtruong1512

Ob4FtMyHTlC8qMpHZFYSiA==

After analyzing the session ID, we identified some suspicious points and may need additional logs for further investigation.

Would it be possible to integrate client-side telemetry and report detailed logs to us for troubleshooting?

Thanks
Vic

5

Thanks, @vic.yang

I’ve added telemetry. Can you help troubleshoot with this session IDs: Akzldh0gQw+d8uWGPCkNFg==, r4r1H2bYRiCx9Nb1umi/Ng==

6

@vic.yang I also encountered a similar case.

1 Like
7

Hey @namlv , @lmtruong1512

Thanks for sharing the additional session IDs with us.

We have identified the root cause and will fix it in the upcoming release (2.1.10).

To further determine the root cause, can I confirm with you whether you have manually set the node-id attribute on the video-player element?

Thanks
Vic

1 Like
8

@vic.yang Thank you, hope the release comes soon!

To further determine the root cause, can I confirm with you whether you have manually set the node-id attribute on the video-player element?

Yes, I have manually set the node-id on the video-player. Can I temporarily remove it as a workaround?

Thanks
TruongLM

9

@lmtruong1512

I have manually set the node-id on the video-player .

This could be the reason for the error.

Video SDK manages the node-id as it is associated with some internal states. Manually setting it may cause state mismatches, leading to issues.

Thanks
Vic

1 Like
10

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