[lang]

Present Perfect

Personal
Projects
Packages
Patches
Presents
Linux

Picture Gallery
Present Perfect

Things I don’t like to see when getting back to work

Filed under: Hacking — Thomas @ 10:59 am

2007-2-19
10:59 am

My screen not responding to the keyboard. Having to log in to it from another machine. Top telling me X is using 75% of my memory, of which 2 GB are real and 4 GB are virtual. Having to kill firefox and instantly seeing the X memory use drop from 75% to 3.6%

How long are we going to have to put up with Firefox’s blatant abuse of memory ? Is it so hard to free a few pixmaps once in a while so that just moving my mouse pointer doesn’t cause swap storms ? Shouldn’t my packager override whatever insane default is causing firefox to ALWAYS HANG ON TO EVERY SINGLE BIT IT EVER ALLOCATES ? I think I’d gladly switch to whatever distro that manages to do the right thing with firefox.

Update: I’ve been getting links from people to pages that explain “how to get Firefox’s memory use under control.” None of these pages address the issue that I seem to have – Firefox is causing X to hold on to way too much memory. Is it storing pixmaps on the X server ? I have no idea. But it is not simply a matter of having a cache of pages.

Regardless – pages that explain how to fix Firefox’s memory are not the right solution. Firefox should be *sensible by default*. Whether they want to provide people options to tweak the size of the bullet, the acceleration of the bullet, and the metal alloy used by the bullet they shoot themselves in the foot with, is entirely up to them.

3 Comments

  1. [...] FireFox/Iceweasel – many people use it, many people want to kill their developers. Why? It leaks memory, it eats memory, it can take 6GB of memory just because there is no more memory available in system. Problem exists in 2.0.x but also in 3.0 trunk version. No solution developed. [...]

    Pingback by Hrw website :: Annoying software bugs — 2007-2-20 @ 12:49 pm

  2. [...] opensource poi! Oggi ho letto che una esperienza molto simile l’ha avuta anche “Thomas Vander Stichele“, che però ha potuto risolvere in tempo, uccidendo [...]

    Pingback by Firefox su Linux: incredibilmente affamato di RAM « pollycoke :) — 2009-12-1 @ 1:16 pm

  3. [...] opensource poi! Oggi ho letto che una esperienza molto simile l’ha avuta anche “Thomas Vander Stichele“, che però ha potuto risolvere in tempo, uccidendo firefox-bin.Chissà che fine ha fatto [...]

    Pingback by Firefox su Linux: incredibilmente affamato di RAM | pollycoke :) — 2010-3-8 @ 2:13 am

RSS feed for comments on this post. TrackBack URL

Sorry, the comment form is closed at this time.

picture