Here are the crash logs from one of the computers:

bp-2afab3e4-f445-486c-bad5-3ff5e2160126

   1/26/2016    8:59 AM

bp-cf0f1b0e-d4f0-4ba7-b367-babb92160126

   1/26/2016    7:50 AM

bp-30428327-876f-4542-8afe-4573a2160125

   1/25/2016    7:35 PM

bp-f23abd7f-064f-44d5-9eef-a2e0f2160125

   1/25/2016    5:09 PM

bp-8c7a7c83-98af-42fc-bfdb-79d642160125

   1/25/2016    3:35 PM

Update: Most of these computers are Win7 PCs, but two are Vista. The first Vista just completed the repair install, and the problem still exists. I will report back on the second.

Here are the crashes from the first Vista machine: bp-49de1559-d181-44f0-a08f-62c252160129 29/01/2016 7:42 AM bp-53682e26-5654-4579-977a-ac3392160128 28/01/2016 5:08 PM bp-1a66defd-1f4b-4b97-bd4e-8abab2160128 28/01/2016 4:55 PM bp-d2316dad-c648-4be8-9e90-475b82160128 28/01/2016 4:50 PM bp-20bb9838-bebf-496f-99aa-c127b2160128 28/01/2016 1:46 PM bp-9f6b0bf1-2f76-4b5f-8604-cf7f92160128 28/01/2016 1:05 PM

Is there any difference if you quit Firefox using the menu? Either:

• "3-bar" menu button > "power" button
• (menu bar) File > Exit

I believe the difference is that the "X" triggers Windows to sent a close window command, while Exit instructs Firefox directly.

Regarding the reason for Firefox hanging during shutdown, there probably is useful information in those crash reports, but after looking at a bug report, it's over my head.

@jscher2000 - Closing with File, Ext or Menu/Power has the same result as the X in the top right corner.

Here are two more crashes from another computer, this one Vista: bp-b7577ec2-395b-41a7-99ee-a1b0f2160201 01/02/2016 09:03 bp-8d96f78e-dad3-4a9a-a0d9-ce7832160129 29/01/2016 10:56

More crashes, this from a Win7 PC. Hopefully someone can make more of them than I can. Are there instructions on deciphering crash logs?

22178efc-512b-4505-8a8c-28c1a1af48eb 01/02/2016 9:37 AM bp-86604432-8b47-4b42-bd41-2cf5f2160129 29/01/2016 1:35 PM bp-a0d2710f-3107-4a1b-9cad-48b1d2160129 29/01/2016 1:19 PM

It seems that Firefox is having a hard time disconnecting, but the crash reports do not seem, to me, to provide enough information to know why. Was there a problem before you used Exit that might be continuing over into the shutdown process?

brundleflyguy said

Are there instructions on deciphering crash logs?

I think there is an article on that somewhere. Hopefully another volunteer has the link. With runtime crashes there often are clues that lead to an obvious culprit, but with these slow shutdown crashes, it seldom is that clear, at least to me.

brundleflyguy said

3)Ran an in-place upgrade or repair install - this seems to fix the problem.

Was that a Firefox update/reinstall or a Windows update/reinstall? If it's Windows, have you tried the System File Checker:

Use the System File Checker tool to repair missing or corrupted system files

jscher2000 said

It seems that Firefox is having a hard time disconnecting, but the crash reports do not seem, to me, to provide enough information to know why. Was there a problem before you used Exit that might be continuing over into the shutdown process?

I notice that websites (such as news.google.ca) take a long time to come up (like almost 30 seconds) when IE and Chrome load them instantly. I've also tried starting FF in Safe Mode (not Windows Safe Mode) but there is no change.

Was that a Firefox update/reinstall or a Windows update/reinstall? If it's Windows, have you tried the System File Checker:

Sorry, I ran an inplace-upgrade or repair install of Windows (I've seen both terms used). That seems to fix the problem with Win7, but not with Vista

I notice that my question seems to have been tagged as an XP problem. It's not. That's just the PC I happened to start the question on. The problem is on Vista and Win7 computers. No Win10 computers have had this problem so far.

I'm up to three Vista computers and four Win7 computers, so either I'm doing something horribly wrong, or there's a problem with FF44.

brundleflyguy said

I notice that my question seems to have been tagged as an XP problem. It's not. That's just the PC I happened to start the question on.

I think it's too late to edit that system detection, but I've never tried because I so rarely post questions here myself...

brundleflyguy said

I notice that websites (such as news.google.ca) take a long time to come up (like almost 30 seconds) when IE and Chrome load them instantly. I've also tried starting FF in Safe Mode (not Windows Safe Mode) but there is no change.

Is there anything special about how your Firefoxes connect, such as a proxy server, private VPN service, or other non-standard routing?

You could check for any modified connection setting (within Firefox) here:

"3-bar" menu button (or Tools menu) > Options

In the left column, click Advanced, then above the page on the right, Network, then the "Settings" button.

The default of "Use system proxy settings" should piggyback on your Windows/IE "LAN" settings, but you also could try "No proxy".

Some users also manually change connection parameters in about:config, or try an extension that makes changes, based on promises that they will make network performance faster. The results of these changes can be unpredictable.

To try to analyze the source of delay, you can try the Network Monitor, which is part of Firefox's web console. It shows multi-colored timing bars which distinguish between issues with the initial connection vs. slow server responses. This article has more info: https://developer.mozilla.org/docs/Tools/Network_Monitor

Are you using "Clear history when Firefox closes" to clear any data?

To see all History and Cookie settings, choose:

• Tools > Options > Privacy > Firefox will: "Use custom settings for history"

• https://support.mozilla.org/kb/Options+window+-+privacy+panel

Are you saying I should be clearing history, or that clearing history would slow things down?

Right now, I'm not clearing history.

I just wanted to mention that I'm having similar problems in Windows XP and Windows 7 with Firefox 44.0. The problem has been much worse in Windows XP for me. https://support.mozilla.org/en-US/questions/1107461. We aren't the only people having these issues. Firefox's Facebook page is full of complaints about the latest update. I hope Version 44.0 will be fixed!

In regard to "I notice that my question seems to have been tagged as an XP problem," the tags seem to have edited themselves, in my case. I'm not sure how that happened. It may have been because I viewed and edited my post with both the Windows 7 and the Windows XP computer - or maybe the contents of the post were scanned for keywords. Another possibility is that one of the volunteers made the adjustment. In the beginning, I only had a tag for Windows 7. Windows XP was added later.

More crashes from yet another Win7 machine: bp-59a98f68-493c-42c2-8e7d-a040d2160202 02/02/2016 7:20 PM bp-a7c3869f-3017-48ee-b582-d86162160202 02/02/2016 5:00 PM bp-9259319a-a3ff-416f-b783-1b8c42160202 02/02/2016 3:03 PM

As an update, disabling IPV6 doesn't make a difference.

Neither does disabling HW acceleration.

However; the x64 version seems a bit more stable. Of course that doesn't help the 32 bit versions of Windows.

Oh well, the x64 version is just as unstable as the x86 version. Is there any word on an update to FF 44?

Version 44 beta 9 has the same problem.

brundleflyguy said

Version 44 beta 9 has the same problem.

Firefox 44 beta releases pre-date the final January release. Did you intend to test Firefox 45, the current beta? https://www.mozilla.org/firefox/beta

The last three reports were all recorded as shutdown hangs that Firefox terminated as crashes. Were there any performance/stability issues prior to exiting Firefox or is the problem always a failure to shut down in a timely manner?

jscher2000 said

Firefox 44 beta releases pre-date the final January release. Did you intend to test Firefox 45, the current beta? https://www.mozilla.org/firefox/beta The last three reports were all recorded as shutdown hangs that Firefox terminated as crashes. Were there any performance/stability issues prior to exiting Firefox or is the problem always a failure to shut down in a timely manner?

Shoot, ok, I'll try FF45 beta.

FF seems to work fine - I can open websites - Youtube works, I can run through peacekeeper.futuremark.com (I use this as a way to exercise FF). Everything seems fine, until I close the browser. Then the process sits in Task Manager after FF appears to close, and about 4 to 5 minutes later, I get a FF crash message.

Could the problem be related to Visual C++ redistributables? On one of the computers, I removed the 2005 and 2008, and so far, things seem to be more stable. Still very long for process to shut down.