To do it fast enough will peg the browser to 100% cpu for that thread. Saw a demo on twitter where they were not reliably able to extract information from the b

To do it fast enough will peg the browser to 100% cpu for that thread. Saw a demo on twitter where they were not reliably able to extract information from the browser. Native, as in not running inside a browser, has been shown to be able to extract information reliably. My guess is the extreme amount of overhead that is required to run JS in an isolated-ish way. I think the point is that a JS based attack, while possible, would be much use outside proof of concept