4 ms·
I'm very interested in your product. However, I'd like to report a strange phenomenon: whenever I open your website's homepage, although it doesn't seem to use
by tianqi 10mo ago
I'm very interested in your product. However, I'd like to report a strange phenomenon: whenever I open your website's homepage, although it doesn't seem to use a lot of memory, my Chrome becomes extremely laggy, and afterwards my entire Mac OS becomes very slow. The first time I encountered this, I couldn't determine the cause. I closed all applications and rebooted my computer. After working perfectly for a while, I reopened your website, and my Chrome and OS became almost unresponsive. After rebooting my computer again, without opening any other applications, just Chrome and your website, and it immediately became nearly unresponsive again. Therefore, while I'm not entirely sure, it seems highly related to your website.
- jjm 10mo agoIt could be the three.js shader on the page that they use which renders in the background. I think you may be able to disable shaders to test but not sure. Been awhile.
- jjm 10mo agoWant to point out, it does run pretty quick on my iPhone surprisingly (and faster than my other dev laptop :-P). Almost forget how much power phones have...
- _ea1k 10mo agoYeah, I had the same experience. It made the page basically unusable for me.
- leetrout 10mo agoIt is also terrible to scroll on iOS with power saver turned on.
- mystifyingpoi 10mo agoSame here.
- nilslice 10mo agoIt's good of you not to jump to any conclusions!
- navane 10mo agoSame on my low end android phone
- brabel 10mo agoOh wow, same thing on my oldish Macbook Air from 2018, using Firefox. Completely unusable.
- deleted 10mo ago[deleted]
- bojangleslover 10mo agoWe fixed this, please try again, also if anyone knows how to run a Three.js shader without exploding people's laptops I am very open to suggestions.
- nextaccountic 10mo agocuriously other pages with three.js demos at the landjng page like svelteflow.dev/ doesn't have this issue i think the trick is to not attempt to render at each frame (that is, don't try to provide something similar to a game engine). just render it based on user input, like the page I linked