And much praise to the Opera team for just not crashing in the first place. I can zoom in the blue square, move around, etc. and the page is still fine after a minute or so leaving it open.
However, i did notice a perceptible bump in memory usage via the System Monitor panel applet. The POC probably exploits a known Memory-allocation bug.
[Currently running Opera 10.10/i686 Linux] Edited: Grammar
* Viewing this page in Firefox 3.6 on Windows caused Flash to crash, taking the browser down with it.
* Viewing it in Chrome on the same machine caused the Flash plugin subprocess to crash, resulting in an error message in Chrome.
* However, no crash occurred in Opera. This despite the fact that 32-bit Opera on Windows does not appear to use isolated subprocesses for running NSAPI plugins.
So what's going on here? Does Opera use some sort of in-process isolation to protect the browser from its plugins? Or is there perhaps some quirk of running in the Opera environment that caused this Flash crash not to be triggered like it was in Firefox and Chrome?
Going off-topic [Opera praise]: These settings instantly turn Opera into the most stable and shockingly scalable 'Research and reference' browser I've used. I only use Firefox3.5.x solely for web-dev, Google Apps, heavy-JS Web 2.0 apps, and Flash-enabled sites of course (with Flashblock as first-line-defence).
Same with the latest versions of Safari, except it takes down all instances of Flash, even those in other pages, which is obviously inferior.