Tree.js breaks down into workers? If not, why do I have all cores loaded?

Question

JavaScript

I ran this example - helloracer.com/webgl
I don't see any explicit division into workers, but the game loads all 8 cores by 35% approximately.
How can this be?
I assume that the browser can transfer data to shaders in parallel, managing not to violate the principle of 1 event loop per 1 thread. But it is not exactly.

Answer 1

There are no workers in three.js, the multiprocess browser itself can split some of the work into processes, but I won’t say why all 8 cores are evenly loaded.