New
#11
Delete updater.exe in the C:\Program Files\Mozilla Firefox directory to prevent it updating and also, reinstall your graphics card drivers. I've seen this happen before on XP and that was the cause
Delete updater.exe in the C:\Program Files\Mozilla Firefox directory to prevent it updating and also, reinstall your graphics card drivers. I've seen this happen before on XP and that was the cause
It's clearly a Firefox issue; took it to their forum (support.mozilla.org if I recall correctly) and didn't get a clear answer, but it's clear that current releases of Firefox use multiple processes. I'll pursue it as time allows; not a priority.
I'm running Firefox right now but there's only one instance shown as running in Task Manager. Normally, I don't use it everyday. However, I started running it every day for the last few weeks. Since then, I periodically get a problem where the graphics driver quits responding for maybe 10 seconds and then restarts. When that happens, Firefox quits responding and I have to close it from Task Manager. I'll be interested in what you find out in regards to your problem.
Not really. Confirmed that Firefox does now use a multi-process architecture. I can live with that (though it's hard on a 3GB laptop). Other, newer issues have taken precedence, sorry!
Have not had to kill any processes in a long while. Currently using v65.0.
Have not seen a problem with the graphics driver hanging (at least not for a long while).
(Did not follow-up on Jeyneko's November post either.)
For what it's worth, my laptop's a low-end Celeron, not a high-performer.
Last edited by billm5; 09 Mar 2019 at 14:18. Reason: unresolved but not reproduced on my machine.
Hi Bill,
MS uses a couple of tools to repair W7
KB976932 (SURT)
sfc /scannow
and to check disk integrety chkdsk /r
With 3Gb Ram your better of using the 32bit version of W7
As for FF its becoming a bit of a resourse hugging browser, try either of these offshoots
Palemoon or Waterfox.
Roy