Chrome vs Firefox performance

Skip to first unread message


Jun 22, 2021, 6:00:50 PM6/22/21
to WebGL Dev List
Hi, I'm having trouble with Chrome on Mac, my code gets much better Web GL performance on Firefox. Does anyone have any ideas/suggestions why that might be the case?

Canvas size is 2160x3840:

Chrome: 7 fps;
Firefox: 32 fps;

The Mac info:
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.106 Safari/537.36
Unmasked Vendor: Intel Inc.
Unmasked Renderer: Intel(R) HD Graphics 530
GL Version: WebGL 2.0 (OpenGL ES 3.0 Chromium)
GL Shading Version: WebGL GLSL ES 3.00 (OpenGL ES GLSL ES 3.0 Chromium)
GL Vendor: WebKit
GL REnderer: WebKit WebG


Ken Russell

Jun 25, 2021, 2:23:45 AM6/25/21
to WebGL Dev List
Could you please provide a test case demonstrating the performance difference, and also provide the contents of Chrome's chrome://gpu page?

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 [email protected].
To view this discussion on the web visit

Valeria Pelova

Jun 25, 2021, 5:27:54 PM6/25/21
Hi Ken, thank you for your reply!

You will need to click on the Benchmark button for the test to run. A Benchmark_Report_Test.txt will be automatically downloaded after the test is done(a few minutes). If you do a soak test and let the app run for a few more minutes the frame rate drops even further.

I'm attaching a file with the gpu info.


MacBook Chrome GPU info.rtf

Ken Russell

Jun 25, 2021, 6:17:22 PM6/25/21
to WebGL Dev List
Hi Valeria,

Thanks for the test case.

I can see the frame rate degradation. The cause is most visible using the Chrome-specific tool about:tracing (just put that in the URL bar), recording, and then "JavaScript & Rendering" trace. Here's a screenshot.

Basically - it looks like your application eventually falls a few frames behind (maybe because it's GPU bound?), at which point Chrome starts waiting for the 3rd oldest frame to finish rendering before it'll start processing the rendering commands for the next one. At this point, it becomes very slow.

Looking at the output of the --show-mac-overlay-borders command line argument (documentation), nothing out of the ordinary seems to be going on.

I have to apologize, but we don't have enough people on our team to diagnose every application in detail. I suggest that you try cutting down your application's rendering and figure out what about it causes this performance drop - if you can eliminate the performance drop over time, that's good information. Or, start from the other direction - a minimal test case just clearing the large canvas to a solid color in pure JavaScript. If you can provoke the slowdown in that configuration, please file a bug at , attach the test case, and post the bug ID here so we can be sure to triage it.


Screen Shot 2021-06-25 at 2.55.36 PM.png
Reply all
Reply to author
0 new messages