Flash/Hang Debugging - Revision history

Mhoye: Remove notification.

2015-02-19T20:02:47Z

Remove notification.

← Older revision		Revision as of 20:02, 19 February 2015
Line 51:		Line 51:
	The dump files will be too large to email or add to Bugzilla. You'll need to upload them to Dropbox or Google Drive, and then [mailto:bsmedberg@mozilla.com?subject=flash_data_dumps share them with Benjamin Smedberg - bsmedberg@mozilla.com].		The dump files will be too large to email or add to Bugzilla. You'll need to upload them to Dropbox or Google Drive, and then [mailto:bsmedberg@mozilla.com?subject=flash_data_dumps share them with Benjamin Smedberg - bsmedberg@mozilla.com].

	Please note that these files may contain personally identifiable information including passwords. We will handle these dumps with a great deal of respect and care, and will not share them outside of Mozilla and - with your permission - our collaborating engineers at Adobe. We will not store or redistribute this data outside of Mozilla or outside of Mozilla's immediate requirements to resolve this issue. ~~As well,~~ Mozilla's copy of this data will be deleted as soon as it is no longer being used to investigate and resolve this issue~~, and you will be notified of this deletion~~.		Please note that these files may contain personally identifiable information including passwords. We will handle these dumps with a great deal of respect and care, and will not share them outside of Mozilla and - with your permission - our collaborating engineers at Adobe. We will not store or redistribute this data outside of Mozilla or outside of Mozilla's immediate requirements to resolve this issue. Mozilla's copy of this data will be deleted as soon as it is no longer being used to investigate and resolve this issue.

	Once you've done that, the last step is to [http://goo.gl/forms/rMCgO5yelu please fill out six questions on this form] about what page you were on, and how you were interacting with your web browser before Flash hung.		Once you've done that, the last step is to [http://goo.gl/forms/rMCgO5yelu please fill out six questions on this form] about what page you were on, and how you were interacting with your web browser before Flash hung.

Mhoye: nits

2015-02-19T20:00:27Z

nits

← Older revision		Revision as of 20:00, 19 February 2015
Line 53:		Line 53:
	Please note that these files may contain personally identifiable information including passwords. We will handle these dumps with a great deal of respect and care, and will not share them outside of Mozilla and - with your permission - our collaborating engineers at Adobe. We will not store or redistribute this data outside of Mozilla or outside of Mozilla's immediate requirements to resolve this issue. As well, Mozilla's copy of this data will be deleted as soon as it is no longer being used to investigate and resolve this issue, and you will be notified of this deletion.		Please note that these files may contain personally identifiable information including passwords. We will handle these dumps with a great deal of respect and care, and will not share them outside of Mozilla and - with your permission - our collaborating engineers at Adobe. We will not store or redistribute this data outside of Mozilla or outside of Mozilla's immediate requirements to resolve this issue. As well, Mozilla's copy of this data will be deleted as soon as it is no longer being used to investigate and resolve this issue, and you will be notified of this deletion.

	Once you've done that, [http://goo.gl/forms/rMCgO5yelu please fill out ~~the~~ questions on this form]. ~~This form asks~~		Once you've done that, the last step is to [http://goo.gl/forms/rMCgO5yelu please fill out six questions on this form] about what page you were on, and how you were interacting with your web browser before Flash hung.

	Some of the information that form asks for will be in "about:support" - you can open about:support the same way you opened about:config earlier.		Some of the information that form asks for will be in "about:support" - you can open about:support the same way you opened about:config earlier.

	Once you have submitted that form, you're done! We hope that by solving this problem, the web will be a better experience for everyone, and Mozilla thanks you for your time and effort.		Once you have submitted that form, you're done! We hope that by solving this problem, the web will be a better experience for everyone, and Mozilla thanks you for your time and effort.

Mhoye: nit

2015-02-19T19:58:43Z

nit

← Older revision		Revision as of 19:58, 19 February 2015
Line 49:		Line 49:
	== Sending the Data to Mozilla ==		== Sending the Data to Mozilla ==

	The dump files will be too large to email or add to Bugzilla. You'll need to upload them to Dropbox or Google Drive, and then ~~share them with~~ [mailto:bsmedberg@mozilla.com?subject=flash_data_dumps ~~email~~ Benjamin Smedberg - bsmedberg@mozilla.com].		The dump files will be too large to email or add to Bugzilla. You'll need to upload them to Dropbox or Google Drive, and then [mailto:bsmedberg@mozilla.com?subject=flash_data_dumps share them with Benjamin Smedberg - bsmedberg@mozilla.com].

	Please note that these files may contain personally identifiable information including passwords. We will handle these dumps with a great deal of respect and care, and will not share them outside of Mozilla and - with your permission - our collaborating engineers at Adobe. We will not store or redistribute this data outside of Mozilla or outside of Mozilla's immediate requirements to resolve this issue. As well, Mozilla's copy of this data will be deleted as soon as it is no longer being used to investigate and resolve this issue, and you will be notified of this deletion.		Please note that these files may contain personally identifiable information including passwords. We will handle these dumps with a great deal of respect and care, and will not share them outside of Mozilla and - with your permission - our collaborating engineers at Adobe. We will not store or redistribute this data outside of Mozilla or outside of Mozilla's immediate requirements to resolve this issue. As well, Mozilla's copy of this data will be deleted as soon as it is no longer being used to investigate and resolve this issue, and you will be notified of this deletion.

Mhoye: Added second mailto link.

2015-02-19T19:58:09Z

Added second mailto link.

← Older revision		Revision as of 19:58, 19 February 2015
Line 49:		Line 49:
	== Sending the Data to Mozilla ==		== Sending the Data to Mozilla ==

	The dump files will be too large to email or add to Bugzilla. You'll need to upload them to Dropbox or Google Drive, and then share them with bsmedberg@mozilla.com.		The dump files will be too large to email or add to Bugzilla. You'll need to upload them to Dropbox or Google Drive, and then share them with [mailto:bsmedberg@mozilla.com?subject=flash_data_dumps email Benjamin Smedberg - bsmedberg@mozilla.com].

	Please note that these files may contain personally identifiable information including passwords. We will handle these dumps with a great deal of respect and care, and will not share them outside of Mozilla and - with your permission - our collaborating engineers at Adobe. We will not store or redistribute this data outside of Mozilla or outside of Mozilla's immediate requirements to resolve this issue. As well, Mozilla's copy of this data will be deleted as soon as it is no longer being used to investigate and resolve this issue, and you will be notified of this deletion.		Please note that these files may contain personally identifiable information including passwords. We will handle these dumps with a great deal of respect and care, and will not share them outside of Mozilla and - with your permission - our collaborating engineers at Adobe. We will not store or redistribute this data outside of Mozilla or outside of Mozilla's immediate requirements to resolve this issue. As well, Mozilla's copy of this data will be deleted as soon as it is no longer being used to investigate and resolve this issue, and you will be notified of this deletion.

Mhoye: Adding some caveats

2015-02-19T19:56:56Z

Adding some caveats

← Older revision		Revision as of 19:56, 19 February 2015
Line 2:		Line 2:
	A number of our Windows users are seeing flash hangs on a regular basis. If you would like to help Mozilla's engineers diagnose and fix those problems for our users once and for all, please follow the process below.		A number of our Windows users are seeing flash hangs on a regular basis. If you would like to help Mozilla's engineers diagnose and fix those problems for our users once and for all, please follow the process below.

	A typical Flash hang happens when a movie or animation starts and Firefox becomes unresponsive for ~~several seconds or~~ minutes.		A typical Flash hang happens when a movie or animation starts and Firefox becomes unresponsive, often for minutes at a time.

	== Getting Started ==		== Getting Started ==
Line 11:		Line 11:
	* Install a Windows tool called [https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx Process Explorer]		* Install a Windows tool called [https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx Process Explorer]
	* An up-to-date copy of Firefox. You can make sure your copy is up to date by looking in the Help menu, and selecting "About Firefox".		* An up-to-date copy of Firefox. You can make sure your copy is up to date by looking in the Help menu, and selecting "About Firefox".
	* An up-to-date-copy of Flash. ~~(VERIFY THAT THIS IS WHAT WE WANT)~~		* An up-to-date-copy of Flash.

	== Setting Up ==		== Setting Up ==
Line 25:		Line 25:
	* Set javascript.options.baselinejit to false		* Set javascript.options.baselinejit to false
	* Set javascript.options.ion to false		* Set javascript.options.ion to false
			* If you are using Nightly, open your Preferences and make sure "Enable E10S (multiprocess)" is unchecked.

	Once that's done, restart Firefox and start Process Explorer, and start browsing the internet as usual.		Once that's done, restart Firefox and start Process Explorer, and start browsing the internet as usual.
Line 38:		Line 39:
	* there should be two FlashPlayerPlugin processes. You want the deeper (second) one - see the diagram below.		* there should be two FlashPlayerPlugin processes. You want the deeper (second) one - see the diagram below.

	The "CPU Usage" column of ~~thesee~~ processes should be zero, or close to it. If so, right-click on each of the three processes and choose Process -> Create Dump -> Create Full Dump, as in the picture below.		The "CPU Usage" column of these processes should be zero or close to zero. If so, right-click on each of the three processes and choose Process -> Create Dump -> Create Full Dump, as in the picture below.

	If the "CPU Usage" column is closer to 1, we're having a different problem; please [mailto:bsmedberg@mozilla.com?subject=Flash_CPU_1 email Benjamin Smedberg] at this point for clarification.		If the "CPU Usage" column is closer to 1, we're having a different problem; please [mailto:bsmedberg@mozilla.com?subject=Flash_CPU_1 email Benjamin Smedberg] at this point for clarification.
Line 48:		Line 49:
	== Sending the Data to Mozilla ==		== Sending the Data to Mozilla ==

	The dump files will be too large to email or add to Bugzilla. You'll need to upload them to Dropbox or Google Drive, and then share them with bsmedberg@mozilla.com~~. Please note that these files may contain personally identifiable information, including passwords~~.		The dump files will be too large to email or add to Bugzilla. You'll need to upload them to Dropbox or Google Drive, and then share them with bsmedberg@mozilla.com.

	--~~- really~~ not ~~happy with that last bit - mhoye ---~~		Please note that these files may contain personally identifiable information including passwords. We will handle these dumps with a great deal of respect and care, and will not share them outside of Mozilla and - with your permission - our collaborating engineers at Adobe. We will not store or redistribute this data outside of Mozilla or outside of Mozilla's immediate requirements to resolve this issue. As well, Mozilla's copy of this data will be deleted as soon as it is no longer being used to investigate and resolve this issue, and you will be notified of this deletion.

	Once you've done that, [http://goo.gl/forms/rMCgO5yelu please fill out the questions on this form].		Once you've done that, [http://goo.gl/forms/rMCgO5yelu please fill out the questions on this form]. This form asks

	Some of the information that form asks for will be in "about:support" - you can open about:support the same way you opened about:config earlier.		Some of the information that form asks for will be in "about:support" - you can open about:support the same way you opened about:config earlier.

	Once you have submitted that form, you're done! We hope that by solving this problem, the web will be a better experience for everyone, and Mozilla thanks you for your time and effort.		Once you have submitted that form, you're done! We hope that by solving this problem, the web will be a better experience for everyone, and Mozilla thanks you for your time and effort.

Mhoye: correction

2015-02-19T15:44:28Z

correction

← Older revision		Revision as of 15:44, 19 February 2015
Line 40:		Line 40:
	The "CPU Usage" column of thesee processes should be zero, or close to it. If so, right-click on each of the three processes and choose Process -> Create Dump -> Create Full Dump, as in the picture below.		The "CPU Usage" column of thesee processes should be zero, or close to it. If so, right-click on each of the three processes and choose Process -> Create Dump -> Create Full Dump, as in the picture below.

	If the "CPU Usage" column is closer to 1, we're having a different problem; please [mailto:bsmedberg@mozilla.com?Flash_CPU_1 email Benjamin Smedberg] at this point for clarification.		If the "CPU Usage" column is closer to 1, we're having a different problem; please [mailto:bsmedberg@mozilla.com?subject=Flash_CPU_1 email Benjamin Smedberg] at this point for clarification.

	[[File:Flash-getfulldump-ProcessExplorer.png\|Process Explorer screenshot of collecting a full dump]]		[[File:Flash-getfulldump-ProcessExplorer.png\|Process Explorer screenshot of collecting a full dump]]

Mhoye: Adding a mai to link.

2015-02-19T15:43:36Z

Adding a mai to link.

← Older revision		Revision as of 15:43, 19 February 2015
Line 38:		Line 38:
	* there should be two FlashPlayerPlugin processes. You want the deeper (second) one - see the diagram below.		* there should be two FlashPlayerPlugin processes. You want the deeper (second) one - see the diagram below.

	~~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.~~		The "CPU Usage" column of thesee processes should be zero, or close to it. If so, right-click on each of the three processes and choose Process -> Create Dump -> Create Full Dump, as in the picture below.
	~~For~~ each of the three processes, choose Process -> Create Dump -> Create Full Dump
			If the "CPU Usage" column is closer to 1, we're having a different problem; please [mailto:bsmedberg@mozilla.com?Flash_CPU_1 email Benjamin Smedberg] at this point for clarification.

	[[File:Flash-getfulldump-ProcessExplorer.png\|Process Explorer screenshot of collecting a full dump]]		[[File:Flash-getfulldump-ProcessExplorer.png\|Process Explorer screenshot of collecting a full dump]]

Mhoye: /* Setting Up */ Minor wording again

2015-02-19T02:26:02Z

Setting Up: Minor wording again

← Older revision		Revision as of 02:26, 19 February 2015
Line 17:		Line 17:
	You'll need to start by opening About:Config to set some preferences. Type "about:config" in the URL bar and hit enter. If this is the first time you've done this, you'll be presented with a warning message telling you to be careful, and you should click the button saying you will.		You'll need to start by opening About:Config to set some preferences. Type "about:config" in the URL bar and hit enter. If this is the first time you've done this, you'll be presented with a warning message telling you to be careful, and you should click the button saying you will.

	Find the following prefs and set them ~~the following prefs to~~ disable the built-in plugin hang monitoring, use the standard Flash sandboxing configuration, and ~~disabling~~ JITs for better debuggability:		Find the following prefs and set them them as listed. This will disable the built-in plugin hang monitoring, use the standard Flash sandboxing configuration, and disable Firefix's Just-in-time JS compiler suite ("JITs") for better debuggability:

	* Set dom.ipc.plugins.hangUITimeoutSecs to 0		* Set dom.ipc.plugins.hangUITimeoutSecs to 0

Mhoye: /* Setting Up */ Minor wording

2015-02-19T02:24:26Z

Setting Up: Minor wording

← Older revision		Revision as of 02:24, 19 February 2015
Line 18:		Line 18:

	Find the following prefs and set them the following prefs to disable the built-in plugin hang monitoring, use the standard Flash sandboxing configuration, and disabling JITs for better debuggability:		Find the following prefs and set them the following prefs to disable the built-in plugin hang monitoring, use the standard Flash sandboxing configuration, and disabling JITs for better debuggability:
	** Set dom.ipc.plugins.hangUITimeoutSecs to 0
	** Set dom.ipc.plugins.timeoutSecs to 0
	** Set dom.ipc.plugins.flash.disable-protected-mode to false
	** Set dom.ipc.plugins.sandbox-level.flash to 0
	** Set javascript.options.baselinejit to false
	** Set javascript.options.ion;false

	Once that's done, restart Firefox and start Process Explorer, and start browsing the internet.		* Set dom.ipc.plugins.hangUITimeoutSecs to 0
			* Set dom.ipc.plugins.timeoutSecs to 0
			* Set dom.ipc.plugins.flash.disable-protected-mode to false
			* Set dom.ipc.plugins.sandbox-level.flash to 0
			* Set javascript.options.baselinejit to false
			* Set javascript.options.ion to false

			Once that's done, restart Firefox and start Process Explorer, and start browsing the internet as usual.

	== Collecting Data ==		== Collecting Data ==

Mhoye: /* Getting Started */ remove some text

2015-02-19T02:23:49Z

Getting Started: remove some text

← Older revision		Revision as of 02:23, 19 February 2015
Line 5:		Line 5:

	== Getting Started ==		== Getting Started ==

	~~First of all: thanks you for your help. Firefox and the Open Web will be better off once we've put this bug down for good.~~

	Before we can begin, you'll need:		Before we can begin, you'll need: