Why is that when i recieved any update for firefox after 35.o.1 that when after i follow all of firefox's advice about how to fix it nothing mentioned fixed it?
When im using this 35.0.1 version everything works fine no youtube crashes or anywhere else. But if i chose to update ...crashes constantly NOTHING mentioned fixing it? Firefox, i believe this is your dam problem looks like you ignore your complaints of which about this are many ...cannot at least list what is or isn't compatible with your latest train-wreck loaded updates?????????
All Replies (12)
Hi johng15, I understand the frustration. If you have crash reports in the profile that this was experienced in, we are happy to further investigate.
- 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.)
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
johng15 said
When im using this 35.0.1 version everything works fine no youtube crashes or anywhere else. But if i chose to update ...crashes constantly NOTHING mentioned fixing it? Firefox, i believe this is your dam problem looks like you ignore your complaints of which about this are many ...cannot at least list what is or isn't compatible with your latest train-wreck loaded updates?????????
bp-d24f463d-36ec-4a7b-905f-ea0e02150325 3/25/2015 bp-90a4a765-a563-4dfc-8ac5-3bd182150325 3/24/2015 bp-ed52dc46-c697-4370-a940-c748f2150324 3/24/2015 bp-c157274f-8191-43fe-8879-1ba582150324 3/24/2015 bp-9a051d4b-13c8-4368-a07d-b67152150324 3/24/2015
The second report is associated with a bug that will not be fixed in version 37. The first is a new one filed that is still currently being investigated. I am sorry about the inconvenience for the crashes. It is possible to disable updates to avoid crashes in the meantime (even though I should not recommend any older version of Firefox)
In order to further investigate the steps to reproduce these crashes, are there any particular settings or websites or steps that are taken right before Firefox crashes?
The crash report flagged these programs;
Signature memmove
nvwgf2umx.dll = Dwm.exe = Microsoft Desktop Window Manager
nvspcap64.dll = NVIDIA GeForce Experience = NVIDIA Corporation
Norton Symantec programs are also listed.
Perform a System File Check to fix corrupted system files http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
See if there are updates for your graphics drivers https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration
Download the current full installers for your NVIDIA and Norton programs.
Wow. Okay, what i don't understand is how UPDATES firefox so strongly puts soo much emphasis and importance on BUT when i "UPDATED" those aforementioned drivers including FIREFOX'S WONDERFUL 36.0 .4 ...this baby was crashing like crazy ...see FIREFOX tells it in it's troubleshooting to go update everything ...BUT as soon as you do IT CRASHES????????? HOW ABOUT FIREFOX UPDATING IT'S HELP AND IMPROVING ITS OWN DAM WEB BROWSER TO WORK COMPATIBLE AND SMOOTHLY LIKE PREVIOUS DOWNLOADS BEFORE IT DOES ...IT LOOKS TO ME LIKE FIREFOX IS BLAMING PEOPLE'S SOFTWARE AND DRIVERS ECT AND PUTTING OUT RUSHED HALF-ASSED WORKING NEW VERSIONS FINE IF THEY WORK FINE FINE IF THEY CRASH WITHOUT RESOLVE THE WHOLE TIME ...I ALREADY WILL TELL YOU MICROSOFT INTERNET EXPLORER AND YAHOO ARE NOTHING MORE ANYMORE THAN MALWARE INFESTED PIECES OF GARBAGE ...WHAT THE HELL IS WITH ALL THE DAM SLACKING AND SEARCH ENGINES AND WEB BROWSERS GOING TO HELL IN A HAND BASKET ...
To think that i was going to upload and use the 64bit version of firefox but idk now....if this is the way all of the new versions are going to perform in the future than the hell with this shit ...i'll go with something else ..we don't need MALWARE CRASHES AND VIRUSES FROM WHAT IS SUPPOSED TO BE TRUSTED ....
I understand that this can be frustrating. However in order to further investigate to confirm, this is the 64-bit version of Firefox which is still being developed.
If the results of the above troubleshooting mentioned by Fred does not make an improvement, the 32 bit version of Firefox would be my next recommendation.
hmmm.......i will play it by experience ...time will say everything ...there is an awful lot posted on the internet about this lately at least it looks like a very big crowd claiming crashes ....idk how big this really is but something is going on id say
The Win64 Beta builds of Firefox 37.0 were not officially supported and were just automated builds. There is no Win64 for Firefox 37.0 Release
The Firefox 38.0 Beta# may be the first to likely have officially supported Win64 Beta's.
Gewysig op
ok well so that doesn't address firefox's 32bit new versions it currently released after 35.0.1...how about those firefox? just going to paper over them and let'r ride and sweep the problems under the rug????? ....i just love how all of a sudden problems start happening after 35.0.1 when nothing like this was ever a problem in the past ......
Good news, one of the crash bugs that you were hitting: 1102612 has been resolved in the most recent version of Nightly (currently version 40) It is currently considered the bleeding edge of development but should result in less crashing. :https://nightly.mozilla.org/