Firefox 32 was running but started misbehaving, so I checked for updates and it updated to 32.0.1. It needed to restart which is fine with me. But it didn't restart.
Do… (read more)
Firefox 32 was running but started misbehaving, so I checked for updates and it updated to 32.0.1. It needed to restart which is fine with me. But it didn't restart.
Double-clicking the Firefox icon on the desktop brought up an error that Firefox was still running but not responding.
In Windows Task Manager I watched firefox.exe's memory usage gradually decrease from around 500MB to 2MB and then stay there for 10 minutes. I created a dump file but am not sure how to send it to anyone who might be interested. A zip of the dump file is 138MB which is far smaller than the raw dump file but I doubt whether Yahoo will let me e-mail a file that size. Next I terminated the process, after which Firefox 32.0.1 was willing to start and is operating normally at the moment.
I see people had the same complaint about Firefox 29 and some other versions, and obviously it isn't fixed yet.
It is possible to code Firefox so that, when starting and detecting that another firefox.exe process is running and not responding, it can ask if the user wants to wait for the other process or terminate the other process. For ordinary users this would be more friendly than teaching them how to open Windows Task Manager, go to the Processes tab, and ignore a warning from Windows about the danger of exiting a non-responsive process.
This is on my wife's PC running Windows 7 64-bit but only 2GB of real RAM, and Firefox only uses around 1GB of virtual memory because she doesn't open many tabs.