I find Google Chrome fast startup and multiple processes, a key when developing Flash/Flex applications. And it’s my preferred target browser for stuff other than HTML.
The problem is that, when debugging a Flash/Flex application and hitting a breakpoint, the Flash Player is stalled, chrome detect this stall and gives you this annoying message every 30, 60, 120, 240, etc’ seconds:
—————————
Plug-in Unresponsive
—————————
The following plug-in is unresponsive: Shockwave Flash
Would you like to stop it?
—————————
Yes No
—————————
It’s very annoying when the context jump to chrome exactly when you intent to click on F6.
Luckily we can use the -disable-hang-monitor startup switch to avoid this annoyance. (All Google Chrome Startup Switches).
Right-click on the desktop link to Google Chrome, select Properties and add the switch to the target:
…ChromeApplicationchrome.exe -disable-hang-monitor
From now on, start Chrome using this link, first, only than you’ll be able to debug in a new tab/window and not get the Plug-in Unresponsive message. The first Chrome window has to be the one started from this link. A bit awkward I know, but that’s the best there is right now.
Trying to add this Startup Switch to the browser parameters inside Flex Builder didn’t worked for me either.