I found it interesting how Chrome and FF handle differently cpu-heavy code like this: arr = new ArrayBuffer(4) arrInt = new Uint32Array(arr) t0 = performance.now(); for (; arrInt[0] On Windows it takes 2.5 secs even on old chrome versions, while it never finishes on the latest FF. The latter's call stack says firefox.exe!TargetNtUnmapViewOfSection(), xul.dll!get_stored_pointer. I wonder if that happens on other platf…
Are you running that in a web page, or in the devtools console? I just tried running it in a web page, with the last line replaced by `console.log(performance.now() - t0);` and on my hardware it finishes in ~1.5 seconds in Firefox and ~2 seconds in Chrome. Similar if I run it in a devtools console like so: (function() { var arr = new ArrayBuffer(4) var arrInt = new Uint32Array(arr) t0 = performance.now(); for (; arrI…
Wow, you are right, thanks. Lesson learned.