6 firefox.exe processes won't end when trying to update

[DN123ABC]

Got a notification to update from 58.0b11 (64 bit) to 58.0b12 (64 bit). Went ahead and hit "Restart", and the main (only) screen went away. Nothing happened. So, I went to Windows 7's Task Manager, and saw there were 6 firefox.exe processes running, many of them using up a LOT of memory. I ended up having to "kill" each one of them individually.

1) How come there are so many firefox.exe processes?
2) How come "Restart" doesn't get rid of them so it can restart itself?
3) What can be done to avoid this going forward?

Thank you.

[therube]

1. e10s, multiprocess
2. how much is a LOT of memory? did you wait long enough to see if the processes would close themselves?
3. patience?

[streetwolf]

This might be the problem that was fixed in Fx59 a couple of weeks ago. It was a regression and it might have showed up in the version of Fx you are now running. When you close Fx it took about 6 seconds before you could restart Fx immediately otherwise Fx will wait.

[DN123ABC]

1. e10s, multiprocess
2. how much is a LOT of memory? did you wait long enough to see if the processes would close themselves?
3. patience?

1. When will they fix this problem?
2. Not sure, but I'll check next time.
3. Ran out, which is why I killed the processes.

This might be the problem that was fixed in Fx59 a couple of weeks ago. It was a regression and it might have showed up in the version of Fx you are now running. When you close Fx it took about 6 seconds before you could restart Fx immediately otherwise Fx will wait.

I waited maybe 3 minutes, and it never restarted after I hit "Restart" on the update. I ended up manually killing all 6 processes.

[streetwolf]

Here's the patch that fixed the problem. Does it sound like your problem? 1420594 – Regression: Latest Nightly needs a longer time to Quit (Spinning Beach Ball appears). My guess is you'll have to wait for Fx59.

[DN123ABC]

Here's the patch that fixed the problem. Does it sound like your problem? 1420594 – Regression: Latest Nightly needs a longer time to Quit (Spinning Beach Ball appears).

No "spinning beach ball". Well, maybe at first, but then it just went away. It was doing nothing for a couple minutes at least.

[streetwolf]

Here's the patch that fixed the problem. Does it sound like your problem? 1420594 – Regression: Latest Nightly needs a longer time to Quit (Spinning Beach Ball appears).

No "spinning beach ball". Well, maybe at first, but then it just went away. It was doing nothing for a couple minutes at least.

Hmmm... Sounds like a different problem. Do a test. Get into Fx then exit out of it and real fast run Fx again. Do you still hang for minutes?

[DN123ABC]

The trouble is it never closes out completely. Still doing it.

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0

[Brummelchen]

there is nothing we can do because your system is the culprit - you were told so many times. i suggest you to ask in a windows forum why your firefox is messing up.

[DN123ABC]

there is nothing we can do because your system is the culprit - you were told so many times. i suggest you to ask in a windows forum why your firefox is messing up.

No, it is Firefox which is killing the system. Once I kill all 6 or 8 Firefox processes, the system responds normally. Thanks anyhow. Anyone else know?

[mightyglydd]

http://kb.mozillazine.org/Creating_a_ne ... on_Windows
https://support.mozilla.org/en-US/kb/pr ... x-profiles