Wondering if 65.0.1 has a memory leak? Had no issues with previous version. Memory seems to creep up and max out eventually.
Had no issues with previous version that I'm aware of. After reboot & update recently seems I have a problem. My usage habit is basically I've usually got hundreds of…
Had no issues with previous version that I'm aware of. After reboot & update recently seems I have a problem.
My usage habit is basically I've usually got hundreds of tabs up on a few different windows up to sometimes 10. Memory seems to creep up with browsing and doesn't really seem to go down even if I close a large number of tabs or whole windows now. A while back there was another version that would leak but it got fixed (within the quantum releases not the really old memory leak that was super bad.) Just wondering if maybe this version has a leak as well.
Side note: I DO love the crash recovery, because it works better than anything else. If I try to close all windows and then relaunch and restore session it never seems to recover everything. But if I crash it via task manager on purpose it has near 100% ability to restore. I'd rather not have to do it that way but it's what works. I'm a very heavy user and outside the norm a bit.
Firefox 63.0 won't open in a new install of Mojave...activity monitor reports memory usage going up to 60+ GB until all application memory is full...
I just installed Mojave (OS X 10.14) and I've downloaded Firefox 5 times so far...all of the version 63.0s install fine but when I run them, they just put Firefox in the …
I just installed Mojave (OS X 10.14) and I've downloaded Firefox 5 times so far...all of the version 63.0s install fine but when I run them, they just put Firefox in the drop-down menu (nothing else) and within a minute or so, consume all of the available (real and virtual) memory - 60+ GB!
I can only Force Quit it. I can't use it at all.
The main reason I updated to Mojave (I was running 10.8) was to use Firefox!
Thanks for helping... Dave
Hello, I'm here more to report a bug than to ask a question, but I couldn't get myself to work with Bugzilla, it asks too many things. So you know how sometimes you open …
Hello, I'm here more to report a bug than to ask a question, but I couldn't get myself to work with Bugzilla, it asks too many things.
So you know how sometimes you open a bunch of tabs in "Private Browsing" just so you have a separate window to close everything at once when it's not needed anymore, well usually in the case of Chrome and Edge, it clears the ram that window was using, instantly no problem... Firefox doesn't really do that and I find it quite worrying if you call it "Private browsing", in fact, closing tabs doesn't really seem to close them at all!
In chrome, when you close 10 tabs you see the ram usage dropping quite clearly, with Firefox it just stays there and it's even worse when I close the whole private window and because I have a normal Firefox window still open, it doesn't clear any ram!
Yesterday I had windows explorer crash because of this and it closed word while I was working on it, go to task manager and Firefox is using 5GB of ram with 5 tabs open... Every damn day I use lots of tabs I have to close Firefox completely and open it again with the same goddamn saved tabs to clear 3gb of memory or more!
Really I want to like this browser, but first of all, this must be a horrible programming practice and second I doubt this is safe at all, keeping closed tabs for hours in memory waiting for the program to close can't be safe, it just can't!
How to reproduce this memory leak? Have Firefox with a normal window open, then open another normal or private browsing window, open a bunch of tabs there, watch memory usage rise, then close that window and watch it not drop at all. Way around it? Close Firefox and re-open. Could it be an add-on bug? Maybe, you tell me if it works with you, but it would still mean there's a bug with Firefox itself.
Really simple, I have no idea why this is a thing, isn't it supposed to have a separate process that clears memory when you close it? I have my doubts it's working like that.