4 ms·
You'd get a better reaction from people if you assumed you're at fault instead of blaming 4 independent browser makers as all being at fault. nookie here menti
by ehsanu1 15y ago
You'd get a better reaction from people if you assumed you're at fault instead of blaming 4 independent browser makers as all being at fault.
nookie here mentions memory use, so why don't you use the profiler in Chrome's web developer tools to find the memory leak (assuming there is a memory leak, as nookie implies). I believe they have some tools to help you in that regard.
- AshleysBrain 15y agoChrome's developer tools never show the memory going above 30mb during the entire game. It's using a heavily optimised engine that creates very little garbage and rarely makes allocations in JS. So the issue appears to be in the browser.
- dlikhten 15y agoI think this quote said it best. I was told this when I started programming... "Don't blame the JVM immediately, there is a very high probability this is just a bug you made, probably some race condition. After all possibilities are exhausted then blame the JVM, you are not even close to that." And there you go. Modify to suit your needs. If every browser crashes, I bet you either has a major bug or found a flaw in a core mathematical component each browser relies on, in either case that flaw must be worked around. So in both cases its on your shoulders.