News for hackers. Stuff that matters.
Re:Firefox 3.6 vs 8.0 by gcp on Tuesday December 06, 2011 @02:10AM (#3318388)
No, but many of the "Firefox crashes a lot" are caused by profiles who have gotten corrupted over the years, and many of the "it eats 2G of RAM" are caused by that and extensions.

Old Firefoxen also tended to fragment their SQLite databases heavily on disk (and in some cases, internally as well), which can show as sluggish response and "hanging" whenever disk I/O is involved. There were changes to ensure that some critical database files don't get fragmented any more, but if you already have those files from an old install you're SOL as it can't defragment them while its using them.

If you have serious performance or memory issues with Firefox, and you're a longtime user, at this point cleaning your profile is probably at least as likely to help as waiting for the next version.

Edit: Just to clarify, the manual cleanup is necessary because uninstalling (and reinstalling) Firefox never deletes your profile. This means that a serious problem can never be fixed by a reinstall - a behavior that probably should be changed.

Re:Firefox 3.6 vs 8.0 by nodata on Tuesday December 06, 2011 @03:28AM (#3318534)
To defrag your databases, first close Firefox then run:

  for i in ~/.mozilla/firefox/*default/*ite; do sqlite3 $i vacuum; done
Re:Firefox 3.6 vs 8.0 by gcp on Tuesday December 06, 2011 @03:54AM (#3318587)
Note that this does not defragment the storage on disk, just the internal SQLite pages. So it's not a complete solution.
Re:Firefox 3.6 vs 8.0 by nirbheek on Tuesday December 06, 2011 @04:04AM (#3318602)
Actually, that command will also rewrite the entire .sqlite file, and if you have enough free space, the filesystem will most likely rewrite it in a contiguous manner.

I tested this with filefrag.