brian: wait, if you get this several times a day, before you let your debugger go, can you check to see how much memory firefox is using? if it isn't near your ulimit, which seems likely....
fwiw, the garbage collector relies on a component which currently does the wrong thing near oom. but if you hit that, it'd flag w/ something else (which i'd definitely spot, since i'm working on it). because of that, there's code in the cc which wouldn't handle oom well (i have an unfinished queue for this stuff)
actually, if it's really the limit, instead of relaxing it, it'd be better if you tightened it (400 or 500).
as to your 40 tabs, assuming ff is using 600mb, that's 15mb per tab (this assumes tabs only have a single page), not including any bfcache, image cache. i don't remember the expected cost per page. but
brian: wait, if you get this several times a day, before you let your debugger go, can you check to see how much memory firefox is using? if it isn't near your ulimit, which seems likely....
fwiw, the garbage collector relies on a component which currently does the wrong thing near oom. but if you hit that, it'd flag w/ something else (which i'd definitely spot, since i'm working on it). because of that, there's code in the cc which wouldn't handle oom well (i have an unfinished queue for this stuff)
actually, if it's really the limit, instead of relaxing it, it'd be better if you tightened it (400 or 500).
as to your 40 tabs, assuming ff is using 600mb, that's 15mb per tab (this assumes tabs only have a single page), not including any bfcache, image cache. i don't remember the expected cost per page. but