91.75 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document
Created attachment 8771788 [details] Mozilla Firefox Warning_Unresponsive Script_dd 17.07.2016.docx User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20160623154057 Steps to reproduce: On this occasion I have tried nothing - except saved as a screenshot and entered in to this procedure in an attempt to learn what to do now and for next time. On the numerous previous occasions, whether it was the same error code recently am uncertain yet have selected each of all three options offered, ie : i) Continue ; ii) Debug script ; iii) Stop script ; Computer froze up completely ; have since then ' refreshed ' Firefox browser, losing, I believe,all add-ons which I had installed. On 21.06.2016 the ' Unresponsive Script Warning ' referred to ' Script : chrome :// browser / content / browser.js: 764 8. Actual results: In between these occasions Msft Update has installed 7 x Updates in WIN10 ; am uncertain how to establish where the error lies in order to take the necessary appropriate stpes to correct this ongoing issue.
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Unable to reproduce bug in OSX Yosemite 10.10.2 using nightly build 50.0a1 (2016-7-18).
Melvyn, Are you doing something in particular when receiving this warnings? Here are a couple of troubleshooting methods that might help: https://support.mozilla.org/en-US/kb/warning-unresponsive-script If the above methods are not helping, could you please try to run Firefox with a clean profile for a while to see if you are still receiving the Unresponsive warnings? https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles Please post here your results.
Closing this as incomplete due to lack of additional information from the reporter. Melvin, please feel free to reopen it if you still have the problem reproducible (on the latest release) and you can provide additional details that could help us reproduce or identify your issue.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.