WebGL getError() is slow in new Chrome Android

[Oleksandr Popov]

Hello.

Is it just me or getError() is way too slow in the Chrome 142 on Android?

My test app checks for gl errors literally on each draw call. Previously this was not a big deal but a few weeks ago I've noticed that the app with ~100 simple draw calls was not able to reach even 30 fps on my phone.

Debugged it for a couple of hours to find that the cause was not in large geometries or uncompressed textures or shaders but the slow check for GL errors. Without it demo runs at solid 120 fps.

Has this been changed in the recent Chrome versions?

Best regards,

   Oleksandr

[Kai Ninomiya]

This is probably related to chrome://flags#use-passthrough-command-decoder. Can you try switching that between "Enabled" and "Disabled" to verify if it makes the difference?

I am surprised that getError() was ever fast enough for your app. It's not supposed to be fast, I think it has always required an IPC roundtrip. But maybe it used to have fast paths, that your app hit, or something, I'm not sure offhand.

-Kai (he/they)

--
You received this message because you are subscribed to the Google Groups "WebGL Dev List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webgl-dev-lis...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/webgl-dev-list/7fa256b5-b0a4-4b8b-8d34-6d6b0f26ae71n%40googlegroups.com.