[Chrome OS] WebGL error - RENDER WARNING: there is no texture bound to the unit 0

Meeting SDK Web
1

Description
As soon as our participant start using our application (and so the Web SDK) to do meetings, tons of error (logs) start to appear.
The participants are using Chrome OS and Chrome Browser, and the mentioned logs can be found below.

This seems to be related to your code, or the data you send (empty texture) - i’m not an expert so please verify that with your engineers, you can find a description of how to fix it here

Not sure if it has a negative impact on rendering performances, but it’s definitely better to clean such error messages.

Error

2021-06-08T03:14:09.042723Z ERROR chrome[1358:1358]: [gles2_cmd_decoder.cc(10718)] [.WebGL-0x2483956a4500]RENDER WARNING: there is no texture bound to the unit 0
2021-06-08T03:14:09.042882Z ERROR chrome[1358:1358]: [gles2_cmd_decoder.cc(10718)] [.WebGL-0x2483956a4500]RENDER WARNING: there is no texture bound to the unit 1
2021-06-08T03:14:09.042941Z ERROR chrome[1358:1358]: [gles2_cmd_decoder.cc(10718)] [.WebGL-0x2483956a4500]RENDER WARNING: there is no texture bound to the unit 2
2021-06-08T03:14:09.042978Z ERROR chrome[1358:1358]: [gles2_cmd_decoder.cc(10718)] [.WebGL-0x2483956a4500]RENDER WARNING: there is no texture bound to the unit 3
2021-06-08T03:14:09.043045Z ERROR chrome[1358:1358]: [gles2_cmd_decoder.cc(10718)] [.WebGL-0x2483956a4500]RENDER WARNING: there is no texture bound to the unit 4

Which Web Client SDK version?
1.9.1 but also probably 1.9.5 and 1.9.6

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

  1. Join a meeting from a Chrome OS and Chrome Browser + inspect chrome OS logs.

Device (please complete the following information):

  • Device: Chrome box
  • OS: Chrome OS latest
  • Browser: Chrome latest
1 Like
2

Hey @nvivot,

Thank you for reporting this, I’ve reached out to our engineering team for their guidance. (ZOOM-283727)

Thanks,
Max

3

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

5

Hi Max,

Are there any news on that topic ?

6

@nvivot

No update so far but I’ve reached back out to learn the status.

I’ll let you know what I hear.

Max

7

Ok, thanks.

I have no idea whether this could cause anything on a chrome OS. We have a couple of regular crashes from people using these chrome box, and these tons of logs every few milliseconds are probably not a good sign.

Hope your team will find some time to investigate on.

Regards,
Nicolas.

8

@nvivot

I haven’t been able to narrow this down myself either. I’m hoping we’ll be able to get to the bottom of this too.

Max

9

@nvivot

Our team got back to me and indicated that this should have since been resolved. Please test with v1.9.7 to confirm that this issue was fixed.

Max

10

Hi Max,

We are going to release the 1.9.7 on production next week. I’ll chek after that if we still see this kind of traces on the chrome boxes.

Thanks.

11

Sounds good, thank you!

Max

12

Hello Max,

Unfortunately I can confirm this error with freezing video in version 1.9.8. The video in speaker view stops with a lot message of this error. Only switching to gallery view and back resolves the freeze.

Best,
Andre

1 Like
13

Hey @andresavic,

Thank you for reporting this. First, please confirm that you have implemented Web Isolation along with the WebCodecs and SIMD Origin Trials referenced there. Then, please provide the version of Chrome that you’re using.

Let me know if that helps.

Thanks,
Max

14

If you are having trouble running WebGL in Firefox, please take the following steps:

Go to about:config in your address bar.
Search for webgl. force-enabled and make sure this preference is set to true.
Search for webgl. disabled and make sure this preference is set to false.
Restart Firefox to apply your new settings.

Regards
Rachel Gomez