How to get debugger working in Chrome July 2018

Yeah, Chrome is the exception to everything as far as file paths go.  Flash Player runs in a jailed filesystem in Chrome, and the paths are different.  Because Chrome ships with Flash Player built-in, getting it to actually run the Debugger introduces some complexity.  You may need to specify some Chrome commandline options to ensure you're always running the Flash Player that you want.

https://peter.sh/experiments/chromium-command-line-switches/  (search for PPAPI or Flash for a good survey of the available options)

You'll also probably want to verify that you're actually running the debugger in Chrome. If you see the Show Redraw Regions option in the context menu, that's a good indicator that you're on the debugger.

Personally, I just use Firefox for debugging to avoid the headache.  Flash Player is more straightforward to configure there, and it keeps Chrome setup for general browsing.

Also, the debugger doesn't write the trace log by default.  You need to enable it in mm.cfg.

Configure the Flash Player debugger version

For Chrome, you should put mm.cfg in the following directory:

• Mac: /Users/<username>/Library/Application Support/Google/Chrome/Default/Pepper Data/Shockwave Flash/System
• Win: %USERNAME%/AppData/Local/Google/Chrome/User Data/Default/Pepper Data/Shockwave Flash/System