Bug#641541: xulrunner-6.0: eats too much (well beyond available) memory

[Mike Hommey]

On Fri, Sep 23, 2011 at 02:06:52PM +0200, Luca Capello wrote:
> found 641541 7.0~b5-1
> found 641541 8.0~a2+20110915042012-1
> thanks
> 
> Hi there!
> 
> On Wed, 14 Sep 2011 12:23:26 +0200, Mike Hommey wrote:
> > On Wed, Sep 14, 2011 at 12:11:01PM +0200, Luca Capello wrote:
> >> On Wed, 14 Sep 2011 11:42:31 +0200, Mike Hommey wrote:
> >> > On Wed, Sep 14, 2011 at 11:37:57AM +0200, Luca Capello wrote:
> >> >> I have now installed xulrunner-7.0 and I will report back what happens.
> >> 
> >> xulrunner-7.0 seems to use the same amount, let me see if it will be
> >> killed someday:
> >> 
> >>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> >>  2886 luca      20   0 1147m 727m  24m S   10 36.3   3:27.64 xulrunner-bin
> 
> Despite the memory consumption (Version: added), xulrunner-7.0_7.0~b5-1
> was never killed, even after having left it open for more than 2 days.
> 
> FWIW, I tried with iceweasel_7.0~b6-1 with 102 tabs (the same as in
> conkeror) and there is no IMHO visible difference:
(snip)

Please note that iceweasel does default to load all the tabs. In 8.0,
there is a visible pref in the "General" section, "Don't load tabs until
selected".

Before that, there was an about:config knob:
browser.sessionstore.max_concurrent_tabs
That pref became browser.sessionstore.restore_on_demand in recent
versions. I don't remember in what particular version is did.

Mike