I found this problem today and chrome cannot debug flex. I believe that if it can be solved, it will make debug a kind of enjoyment ^
I searched the information online and summarized it as follows:
Bytes ------------------------------------------------------------------------------------------------------------------------
Flash Player debug failure in Google Chrome-[flex]
After changing to Windows 7, I encountered a new problem today, that is, the debugging program running in flex cannot correctly connect to the Flash Builder 4 debugger when running in Google Chrome.
I am depressed for a long time. I have repeatedly uninstalled and installed Flash Player debug, and even downloaded and installed the old version. The problem persists, and it is not a problem with the definition of IPv6 hosts. I ran well on the original Vista. How can I migrate it to Windows 7? In order to diagnose the problem, I tried whether IE8 can be properly debugged. The result is that IE8 is slow, but the connection to debug is normal. After careful consideration, IE8 runs the debug version, while chrome runs the normal version.
In this way, I thought that flash Builder 4 must be okay. ie runs well and won't be a problem with the Flash Player debug version, because it used to run normally. I uninstalled all the flash players and tried to open the flash in various browsers. IE is no longer able to play the flash, but Chrome is still playing, so there must be a problem here, we have been using Chrome's built-in flash player, but it is not a debug version, so we certainly cannot connect to the debugger.
The possible cause is Google Chrome's plug-in. Open chrome: // plugins/in the address bar of Google Chrome /. After reading it, we found two flash
PLAYER:
Shockwave
Flash-version :,
Note: |
Shockwave Flash 10.1 R53 |
Location: |
C: \ Users \ Tony \ appdata \ Local \ google \ chrome \ Application \ 5.0.375.23 \ gcswf32.dll |
Shockwave Flash-version: 10, 0, 45, 2
Note: |
Shockwave Flash 10.0 r45 |
Location: |
C: \ windows \ system32 \ macromed \ Flash \ npswf32.dll |
Note: Open chrome: // plugins/and then open plug-in details: Disable: C: \ Users \ ant \ appdata \ Local \ google \ chrome \ Application \ 13.0.782.107 \ gcswf32.dll.The version is updated with the built-in version (not the debug version), so it is used first to play flash. The debug version installed by myself is naturally overwritten. It seems that Google is Adobe's fans, and it also helps put Flash Player's built-in applications. Disable the built-in version. Try flash again. This is the debug version. Debug Flex again and connect to the debugger normally.
Haha. Great.
Bytes ------------------------------------------------------------------------------------------------------------------------
Adobe Flash debugger player 10.1 for chrome is: http://download.macromedia.com/pub/flashplayer/updaters/10/flashplayer_10_plugin_debug.exe
Bytes ------------------------------------------------------------------------------------------------------------------------
I want to note that flashplayer_10_ax_debug.exe is used for IE kernel, and the plug-in above is used for non-ie kernels such as chrome. Disable Standard Flash Player in chrome plug-in options. When re-installing the debugversion flashplayer, remember to use uninstall_flash_player.exe (available on the Adobe official website) to completely uninstall the old version of flashplayer. Here, remember that the deleted control panel is incomplete. Open flex, F11, and OK. It's really amazing. People no longer want to recall sogou's painful times ......