I’ve been using Ubuntu (8.04 then 8.10) reasonably heavily over the last 12 months or so as my main operating system on two of my home computers (a Dell Mini 9″ and a quad core desktop).
I’ve been pretty happy with it except for the infuriating habit Firefox has for “locking up” periodically. The symptoms of this include non-reponsiveness, screen freezing and even the computer being unusable for 30 seconds at a time. The only clue I had was there seemed to be large amounts of disk usage.
After a while bitching and moaning about it I got so annoyed I started looking for a fix.
The first thing I tried was the Chromium Linux nightly builds. Google says “blogging about this isn’t helpful”, so I won’t except to say that I’ve got pretty high expectations of Chrome on Linux and so far I haven’t had to re-apprise that.
All the same, I wanted to fix Firefox. The next thing I tried was moving Firefox cache to a RAM drive. That’s pretty easy – just set it to use a directory under /dev/shm/ for the cache location.
I think that improved the situation marginally, but not enough to call it a fix.
The comments on that bug are quite long, but the story is this:
- Firefox uses SQLite as a database for its history and bookmarks.
- SQLite, being a database is very concerned about data integrity, and to implement this it relies on the fsync system call.
- fsync has performance issues on ext3 filesystems. See for example, http://lwn.net/Articles/328363/:
The problem, in short, is this: the ext3 filesystem, when running in the default data=ordered mode, can exhibit lengthy stalls when some process calls fsync() to flush data to disk. This issue most famously manifested itself as the much-lamented Firefox system-freeze problem, but it goes beyond just Firefox.
- SQLite has a no-sync mode, which trades reliability for performance.
- Firefox can use this mode via a config setting.
So the outcome of all that is this:
Create a new config key “toolkit.storage.synchronous” and set it to the integer 0 to stop Firefox lock-ups on Linux (but be aware that there is some chance a power failure could cause loss of your history and/or bookmarks).