question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

WebGL1Renderer now faster than WebGLRenderer after browser update

See original GitHub issue

Hi!

I was using Three.js this month for testing and everything was fine.

After I update Brave, today, all my code was running really slow, from 59 fps to 14-15 fps The issue happened in both of the video cards in the notebook:

  • Intel HD Graphics 630 1536 MB
  • Radeon Pro 560 4 GB

Tried a lot of tests:

  • Updated r138 to r139: still slow
  • Put just 4 objects in scene: still slow
  • Changed WebGLRenderer to WebGL1Renderer: got speed back!

The renderer init code before: const renderer = new THREE.WebGLRenderer({ antialias: true, powerPreference: "high-performance" });

This is what the renderer init code looks now: const renderer = new THREE.WebGL1Renderer({ antialias: true, powerPreference: "high-performance" });

Maybe it’s a Chromium 99 vs 100 issue? Can try to test in real Chrome browser and supply a full source code with different models if needed

To Reproduce

Brave macOS version with the WebGLRenderer slow and WebGL1Renderer fast: Version 1.37.109 Chromium: 100.0.4896.60 (Official Build) (x86_64) Download link: https://github.com/brave/brave-browser/releases/tag/v1.37.109

Brave macOS version with both WebGLRenderer and WebGL1Renderer fast: Version 1.36.117 Chromium: 99.0.4844.74 (Official Build) (x86_64) Download link: https://github.com/brave/brave-browser/releases/tag/v1.36.117

Platform:

  • Device: Desktop
  • OS: macOS (12.3 (21E230))
  • Browser: Chromium based
  • Three.js version: r138 and r139

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:11 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
Mugen87commented, Apr 1, 2022

Closing. This issue can’t be fixed in three.js.

I suggest you report the issue at https://bugs.chromium.org/p/chromium/issues/list or continue the discussion at https://github.com/brave/brave-browser/issues/22030.

0reactions
LeviPesincommented, Apr 6, 2022

This appears to be some other Chromium 100 bug, not https://github.com/brave/brave-browser/issues/22030.

Read more comments on GitHub >

github_iconTop Results From Across the Web

WebGL1Renderer – three.js docs
This version of the renderer will enforce a WebGL 1 rendering context. Constructor. WebGL1Renderer( parameters : Object ). Creates a new WebGL1Renderer.
Read more >
Three.js: How is using two or more renderers affect ...
In general, CSS renderers do not work with WebGL nor a canvas element so there is no side effect regarding WebGLRenderer 's tasks....
Read more >
What I Wish I'd Known About Three.js | by Ian Henry Walls
A basic renderer can be created with the line const renderer = new THREE.WebGLRenderer() . The next step is appending the renderer to...
Read more >
How to use lighting and WebGLRenderer in Three.js
js is a JS graphics library that is used for rendering 3D graphics in browsers. Major graphics organizations use Three.js for creating and ......
Read more >
Setting the position of objects in threejs
When it comes to mutating the position attribute of buffer geometry that ... objects than can then be used to set the position...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found