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. Dale :-) :-)
