Everything appears to be operating correctly in the demo. Although I'm not sure where the issue lies, I can offer some insights.
Typically, a web browser does not require a dedicated graphics card to function. However, when a tab using WebGL is opened, it may call upon hardware acceleration which could trigger the fan to turn on, irrespective of the specific requirements of the WebGL application. This is more of a hardware or firmware issue. I encountered a similar situation in the past, only to discover that my laptop was faulty.
To troubleshoot, I recommend ruling out potential causes. Conduct a GPU benchmark or test other graphics-intensive applications (such as games) to see if similar problems persist. If not, focus on investigating the WebGL aspect. Experiment with different browsers for this demo, as well as other WebGL applications, to determine if the issue is specific to Three.js apps, WebGL in general, or unique to this particular demo.
- If the problem persists across all browsers and applications, it may indicate a deeper underlying issue with your system configuration that is beyond my expertise.
- If the problem is isolated to this demo regardless of the browser used, while other apps function properly, the issue likely lies in the interaction between WebGL, GLSL functions, and your graphics card. Consider reaching out to the WebGL development community and graphics card manufacturers for further guidance.
- If the problem only occurs in a single browser, it could be related to the browser settings or the browser itself. Reinstalling the browser or contacting the developers for assistance may help resolve the issue.
- If the issue is specific to one browser and this demo, it indicates a problem specific to the browser and Three.js. Conduct a more in-depth benchmark of the demo and consider reaching out to the Three.js developers for support.
Apologies if this response is lengthy, but it exceeded the character limit for a comment.