4 ms·
Kills Firefox Developer Edition on MacBook Air. I still can see the demo, but the entire browser becomes unresponsive and the only option is to force-close it.
by kolev 12y ago
Kills Firefox Developer Edition on MacBook Air. I still can see the demo, but the entire browser becomes unresponsive and the only option is to force-close it.
- Gracana 12y agoUses all the CPU my single firefox thread can take, on both my home computer and work computer. I couldn't figure out what was wrong at first because it rendered beautifully and would respond enough to eventually start a(n unplayable) game after I mashed 'x' a bunch. It was only once I tried to close the tab that I realized it was being incredibly unresponsive.
- kreldjarn 12y agoTo be fair, it's incredibly CPU-heavy. It uses an iterative approach to calculate the forces exerted on the grid, so for each frame it calculates the force exerted on each node a set number of times. (See http://en.wikipedia.org/wiki/Verlet_integration http://en.wikipedia.org/wiki/Verlet_integration) However, this shouldn't be so heavy that the Firefox JS engine struggles with it...
- Gracana 12y agoYeah the weird thing is that aside from being unresponsive it seems to run fine. The lines move around and the fabric stretches and waves smoothly. That's on an older i3, and a newer 3.GHz i5. I bet it works properly in chrome. I like Firefox but I always seem to have performance issues with it.