On Sat, Feb 17, 2018 at 10:57 PM, Dale <[email protected]> wrote: > R0b0t1 wrote: >> On Sat, Feb 17, 2018 at 9:11 PM, Dale <[email protected]> wrote: >>> R0b0t1 wrote: >>>> Hello List, >>>> >>>> This isn't normal. Is it due to the new process model? I think I read >>>> that now they emulate chrome, which possibly means both browsers are >>>> unsuitable for use. Firefox will require its threads be OOM killed if >>>> not closely monitored. >>>> >>>> If it can be fixed - can anyone explain? >>>> >>>> Cheers, >>>> R0b0t1 >>>> >>>> >>> >>> Have you checked to see what in Firefox is using that memory? >>> about:memory Then click on Verbose and then Measure. In the past, I >>> have found websites that are just awful at loading everything Firefox >>> has and usually for no good reason. It's one reason I use adblock, with >>> some custom blocking not related to ads, and script blocking tools as >>> well. I can give those memory hungry things a toss in the trash before >>> they even load. >>> >>> Maybe that will help. Of course, it could be just Firefox being >>> Firefox. I have seen mine use 2GBs in the past but never that much. :/ >>> >>> Hope that leads to a clue. >>> >> It's a good tip, but the report seems to be a bit optimistic. Firefox >> claims there are 5 processes using ~500MB each, yet if I close Firefox >> 10G is suddenly free. Regardless of whether or not Firefox thinks it >> is using the memory, the kernel thinks it is, because OOM killer >> triggers. >> >> It may or may not be related to certain webpages, I can't especially tell. >> >> Cheers, >> R0b0t1 >> >> > > I'm stuck on Firefox 56 at the moment, addon issues. Anyway, I've had > Firefox, and Seamonkey, to become quite the memory hog before too. > Sometimes the memory things works but it's hard to grasp at times. > Other times, it just provides no help at all. I was hopeful that it > would point out a particular addon or website for you. > > I run multiple profiles here because I have to be logged into the same > site but as different users. Sometimes the best thing to do is > restart. I have found that some sites take up a chunk of memory but > when I close all the tabs for that site, it doesn't seem to release that > memory until I restart Firefox. I don't know if it is the website or > Firefox because sometimes it seems to work as it should and sometimes > not, even with the same site. > > It seems that any web browser that has a lot of bells and whistles is > just going to be a memory hog. I have to admit tho, 10GBs is > excessive. That would make me cringe a bit too. > > Maybe the next update will fix it??? >
Right, restarting Firefox is a solution, but not the best. I hope they roll out the compartmentalized profiles soon.
