Firefox 44.0 crashes in Windows XP SP3 and may cause Windows to crash
I just updated to Firefox 44.0, and I'm now getting a "Mozilla Crash Reporter" when I try to close the Firefox browser. The Crash Reporter will not submit any reports. This is happening over and over again on my older computer, which has Windows XP SP3 Media Center Edition.
The issue may have something to do with the browser not closing fully when asked to. I'm not sure about this.
Firefox Version 43._ always worked perfectly on this computer. Should I just wait until Mozilla fixes this issue?
EDIT: Oh no! The same thing just happened in Firefox 44.0 on my Windows 7 computer, except that in this case the crash report was submitted. That's Windows 7 Professional x64.
Muudetud
Valitud lahendus
For what it's worth, I have used the Firefox ESR for years (extended support release). Currently running 38.6.0.
Firefox Extended Support Release for Your Organization, Business, Enterprise - Overview — Mozilla
It has always been extremely stable for me under XP Professional. The benefit of the ESR is that you are less likely to have new problems introduced into the browser, since the ESR is focused on security updates and NOT new features.
Loe vastust kontekstis 👍 0All Replies (8)
When I started having problems with Firefox 44, I began following Firefox's Facebook page. I see that on January 31, 2016 alone, one or two other people reported that the latest Firefox update "crashed their computer." I'm not counting reports of Firefox crashing, here - just "computers crashing." This is serious.
I'm not whining, by the way. ;) I just want to fix this or have the problem solved. I'll do more reading. I'll look into possible causes of Microsoft TCP/IP Driver-related "blue screens" too. Unfortunately, I'm quite inexperienced because I've never had a major problem with Firefox or Windows before.
Muudetud
So, I've looked up the two different crash signatures which were reported on my Windows XP computer. Most of the Firefox crashes on this computer didn't make it into the "crashes:about" list. I'll try later to find a record of those crashes in some different way (if possible).
Of the reported crash signatures, one doesn't have any bug information.
The other, "shutdownhang | WaitForSingleObjectEx | WaitForSingleObject | PR_WaitCondVar | mozilla::CondVar::Wait", has bugs 1219672 and 1215970 associated with it. This crash signature is one of Firefox 44's "top crashers" (ranked # 2). The only clue I could find to a cause is that it may be associated with Skype. Information: https://bugzilla.mozilla.org/show_bug.cgi?id=1215970 . Let me see if my XP computer has Skype... No, it doesn't.
Muudetud
Rosa2 said
Isn't a Windows blue screen a serious risk to a computer? Windows
No, they BSOD in itself isn't a serious risk. Repeated BSOD crashes may cause Windows corruption, but the big concern is the underlying problem that is causing the BSOD.
I think the immediate cause of the BSOD was the repeated Firefox crashes. However, I'll do some reading on that particular blue screen message as soon as I have a chance. I may turn out to be mistaken about the connection with Firefox.
Have you looked up any of your Firefox crash signatures, brundleflyguy??
EDIT: I'm now finding useful info on possible causes of the blue screen crash. I'm going to update some drivers on my XP machine and look into this more carefully.
Muudetud
jscher2000 said
Yes, blue screen crashes are bad. But also very rare.
Sorry that I accidentally marked your reply as unhelpful. I don't know what came over me! My finger simply clicked in the wrong place. I appreciate your help very much. It may take me a while, but I feel slightly more optimistic about finding the cause of the blue screen crash. After that, I may try opening Firefox again.
Muudetud
Valitud lahendus
For what it's worth, I have used the Firefox ESR for years (extended support release). Currently running 38.6.0.
Firefox Extended Support Release for Your Organization, Business, Enterprise - Overview — Mozilla
It has always been extremely stable for me under XP Professional. The benefit of the ESR is that you are less likely to have new problems introduced into the browser, since the ESR is focused on security updates and NOT new features.
I'll look into this, Stephen. Thank you!
moderator selected the "solution" for this thread
Overall, way too many edits made by the OP in this thread - edits that were made many hours to a few days after a particular posting was made.
IMO, it is generally unnecessary to edit a posting any more than a few minutes after a posting has been submitted to correct a mis-statement or correct grammar, and it is especially bad after contributors have responded to the particular posting and maybe changing the context of what was originally posted, towards which contributors responded.
When further information is posted or a clarification for a particular posting is deemed necessary, it is more appropriate to make another posting with the clarification or further information