allat.blogg.se

1. #Mozilla firefox developer 64 bit memory leaks update
2. #Mozilla firefox developer 64 bit memory leaks driver

This problem, to me, appears very similar to the problem I originally described, where Firefox had trouble rendering UI elements when it was about to run out of memory.

#Mozilla firefox developer 64 bit memory leaks update

I'm leaving the question open for actual, factual answers, just in case.Īfter the update that disabled custom add-ons I had to change to Firefox Developer Edition (FDE) (64-bit, with electrolysis enabled) and the memory leak seems to be back (FDE will accumulate about 2GB of memory split between its two processes within a few days), additionally with another issue that sporadically occurs, which is FDE refusing to render any and all webpages (even the ones already loaded) and just displaying a white page with a loading indicator in the middle.

#Mozilla firefox developer 64 bit memory leaks driver

This leads me to believe that a faulty (possibly outdated) driver or system library was the culprit - although I can't tell which one in hindsight. You guys should run firefox on a machine with less that 4gb ram, not what you probably run on, as in. Memory usage is stable between 600 MB and 1100 MB (which might have to do with the amount of tabs and addons I use). 1st thing that comes to mind is a potential memory leak. Here is an about:memory profile at 1.4GB: Īfter upgrading from Windows 7 to Windows 10 the leak seems to be fixed (for now). I have also disabled a windows titlebar addon in an attempt to find causes outside of Firefox, so far without success. It also stays longer between 1 and 2 GB with this build, but will eventually run above. I have now switched to the 64-bit Windows build, which delays the rendering glitches until closer to the 4GB mark. What else can I do to try and resolve this annoying problem? The only thing that seems to help is to run Firefox in safe-mode, but that is a very inconvenient thing to do.įirefoxes on other machines synced to the same profile do not exhibit this behaviour. Uninstall, delete all Mozilla folders from AppData, reinstall.At some point, when it reaches the 2.2GB mark, it starts having rendering glitches and then crashes out eventually with a message indicating that GDI failed to allocate new memory. My firefox has been continually leaking memory for years now (as in, it started several versions back, currently on 42.0).