Firefox crashes
When I upgraded to version 49 and higher FF crashes -- with FF not responding. Event viewer says it is an application hang error 1002.
When I roll back FF to version 48 everything is fine -- no more crashing, no more application error.
I'm running windows 10 on a 64bit system.
Any ideas?
Alle antwurden (4)
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
The crash report is several pages of data. We need the report numbers to see the whole report.
- Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
- Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
This is an application hang issue and does not show up as a crash report in the about:crashes. It shows up in the Windows 10 event viewer log as event id #1002 which a windows application hang error.
The message says that Firefox stopped interacting with windows and was closed. I closed it -- otherwise it would still be buffering with the program not responding message showing.
Again -- this does not happen in FF version 48 but happens in FF version 49 and FF version 50.
I have rolled back to FF 48 and am not experiencing the application hang. Have not tweaked anything else -- just rolled it back to FF 48.
could you go to the firefox menu ≡ > help ? > troubleshooting information, copy the contents of that page and paste them here into a reply on the forum? this might give us a clue what is going on...
information retracted again at the behest of the topic owner