Confirm, emeritus
1,217
edits
Changes
Flash hang debugging instructions
This page is intended for people who see Flash hangs on a regular basis. It contains instructions for how to collect additional information about these hangs. These instructions are Windows-specific.
== Setup ==
* Install and run [https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx Process Explorer]
* Set the following prefs to disabling the built-in plugin hang monitoring and use the release configuration:
** dom.ipc.plugins.hangUITimeoutSecs;0
** dom.ipc.plugins.timeoutSecs;0
** dom.ipc.plugins.flash.disable-protected-mode;false
** If you are using e10s enabled Nightly, disable e10s in the Firefox preferences. (Unless the hang is e10s-specific.)
== Collecting Data ==
When you experience a Flash hang, use Process Explorer to collect full debugging dumps from three processes. In process explorer you should see a list of nested processes including firefox.exe.
You want to select the following processes:
* firefox.exe
* plugin-container.exe (if there is more than one, you want the one with a child FlashPlayerPlugin process)
* there should be two FlashPlayerPlugin processes. You want the deeper (second) one.
Check the CPU usage of the processes and make sure that it is close to 0. If it is close to 1, STOP NOW and ask Benjamin Smedberg for assistance.
For each of the three processes, choose Process -> Create Dump -> Create Full Dump
After you have collected the data, you should be able to kill the plugin-container process in process explorer to un-hang Firefox.
== Sending the Data to Mozilla ==
The dump files will be too large for bugzilla. Upload them to a file-sharing service like dropbox or google drive, and share them with bsmedberg@mozilla.com. Do not share these files with everyone: they are likely to contain some personal information such as passwords or bookmarks.
File a bug at bugzilla.mozilla.org product "Core" component "Plug-Ins". Include the following information:
* What you were doing at the time of the hang, as exactly as possible.
** Was there only one tab open, or multiple tabs?
** Did you move the mouse over the plugin content, click on it, or type at any point?
** Did you choose any full-screen mode?
* The exact build of Firefox that you were using at the time. The best way to collect this is copy it from about:support in the browser.
* A link to the dump files on dropbox/google drive.
* If you are willing, a note that it is acceptable to forward these dump files to Adobe engineers to aid with debugging.
== Setup ==
* Install and run [https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx Process Explorer]
* Set the following prefs to disabling the built-in plugin hang monitoring and use the release configuration:
** dom.ipc.plugins.hangUITimeoutSecs;0
** dom.ipc.plugins.timeoutSecs;0
** dom.ipc.plugins.flash.disable-protected-mode;false
** If you are using e10s enabled Nightly, disable e10s in the Firefox preferences. (Unless the hang is e10s-specific.)
== Collecting Data ==
When you experience a Flash hang, use Process Explorer to collect full debugging dumps from three processes. In process explorer you should see a list of nested processes including firefox.exe.
You want to select the following processes:
* firefox.exe
* plugin-container.exe (if there is more than one, you want the one with a child FlashPlayerPlugin process)
* there should be two FlashPlayerPlugin processes. You want the deeper (second) one.
Check the CPU usage of the processes and make sure that it is close to 0. If it is close to 1, STOP NOW and ask Benjamin Smedberg for assistance.
For each of the three processes, choose Process -> Create Dump -> Create Full Dump
After you have collected the data, you should be able to kill the plugin-container process in process explorer to un-hang Firefox.
== Sending the Data to Mozilla ==
The dump files will be too large for bugzilla. Upload them to a file-sharing service like dropbox or google drive, and share them with bsmedberg@mozilla.com. Do not share these files with everyone: they are likely to contain some personal information such as passwords or bookmarks.
File a bug at bugzilla.mozilla.org product "Core" component "Plug-Ins". Include the following information:
* What you were doing at the time of the hang, as exactly as possible.
** Was there only one tab open, or multiple tabs?
** Did you move the mouse over the plugin content, click on it, or type at any point?
** Did you choose any full-screen mode?
* The exact build of Firefox that you were using at the time. The best way to collect this is copy it from about:support in the browser.
* A link to the dump files on dropbox/google drive.
* If you are willing, a note that it is acceptable to forward these dump files to Adobe engineers to aid with debugging.
