Note: If Internet Explorer consistently crashes when viewing Flash content, the crash may be the result of ActionScript code, system performance, and/or memory allocation.

To optimize ActionScript code and prevent memory issues that may lead to a crash, delete variables when you no longer need them. While it is better to delete variables you no longer need, you can set unused variables to null to enhance performance.

Reporting a crash to Adobe

Please follow three steps to report a crash/freeze issue to Adobe:

Create a Flash Player crash log

On Mac OS

Use the log generated by the Mac OS X Crash Reporter. For information about this log, see Apple Technical Note TN2123.

On Windows XP or Vista

  1. Open Notepad or another text editor:
    • Start> All Programs> Accessories> Notepad
  2. Create a text file with one line: CrashLogEnable=1
  3. Save the file as: c:\windows\system32\macromed\flash\mms.cfg
  4. Generate a crash in Internet Explorer. Write down ALL URLs open at the time (windows or tabs).
  5. Open the Run dialog:
    • Start > Run.
  6. In the dialog, type the following:
    •  C:\Documents and Settings\[username]\Local Settings\Temp (Windows XP)
    • C:\Users\[username]\AppData\Local\Temp\ (Vista)
  7. Hit ENTER or click OK
  8. In the directory that opens, find files that have the extension *.mdmp, or start with “player_crash_log”

Submit your crash log via the Flash Player public bugbase

Follow the instructions in the article "Introducing the Flash Player bug and issue management system."

Create an Adobe support case

  1. Ensure that you are developing using a supported Adobe product, or have purchased a support contract. For more information about support options, see the Adobe support programs page.
  2. Submit an Adobe support ticket through the Adobe Support Portal for the product you are developing with. An AdobeID and login is required. 
  3. Include the information listed below to help us diagnose the crash:

    • System information (OS version, etc)
    • Browser information
    • Number of tabs open
    • URL
    • Reproduction steps
    • Link to the Flash Player public bug report submitted above. 

      NOTE: If for some reason you are unable to create a Flash Player public bug as described above, please attach .mdmp crash log files to your webcase.  

      NOTE: Crash-related bug reports are immediately made private to prevent exposing your system information to the public. After filing the bug report you will not be able to see it again. Please note the bug report number. 
    • When opening a developer-specific support case, please supply FLA/MXML source that reproduces the issue.


This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy