Debugging with Google Chrome and Flash Player 10.1

[url]http://polygeek.com/2780_flex_debugging-with-google-chrome-and-flash-player-10-1[/url]

After updating to Flash Builder 4.1 and Flash Player 10.1 I found that I could no longer debug with Google Chrome – my preferred debugging browser. A quick search yielded this fix buried in the comments. I’m reposing here to help more people find the solution that Anand Gaurav found.

Here is how you can install debug Flash Player on Chrome:

1. Type about:plugins in the address bar

2. Disable the Adobe Flash Player (Shockwave player) plugin.

3. Install the debug version of Flash Player manually.

In case you already installed debug Flash player, it should have been listed already in the plugins and you are ready to go.


You can see that Shockwave Flash is listed twice but in two different locations. The one in the Windows\Sys\ folder is the one that I want to use. The other one that I disabled is the regular old Flash Player.

I use Google Chrome to debug because it loads faster than any other browser and FireFox is my primary browser and I don’t want my tab bar filled up with testing crap. You can read more about making Google Chrome your default Eclipse Debugging browser here.

There is also a caching issue that you might run into while using Chrome – or any browser – for debugging. In that case here’s a great fix to make sure that your debugging browser never runs cached SWFs.