Straw poll: What browser do you use?

I'm just wondering, since firefox/iceweasel seems to be getting unusable. I
have a 2.2GHz C2D box with an nvidia card at home, and a 3.0GHz C2D with a
(lame) ATI card at work. I find that firefox (or xulrunner-stub) have memory
leaks, and after a couple of days, it eats up a significant amount (10-30%)
of memory. The work box has 3GB and the home box has 4GB. It also eats up a
significant amount of CPU.

This morning, after idling all weekend, iceweasel on my work system was
chewing up between 70 and 100% of my cpus, and scrolling pages were
hesitating for several seconds.

So what do others use?
--b

Relevant Pages

  • Re: pcib allocation failure
    ... pcib1: attempting to grow prefetch window for ... attempting to grow memory window for ... cpu0: on acpi0 ... <ACPI PCI bus> on pcib0 ...
    (freebsd-current)
  • Next July 27: boot failure(hang) on x86_64 box.
    ... Freeing unused kernel memory: 1360k freed ... ACPI: PM-Timer IO Port: 0x488 ... CPU: L2 Cache: 1024K ... # AX.25 network device drivers ...
    (Linux-Kernel)
  • [PATCH] Document Linuxs memory barriers [try #3]
    ... The attached patch documents the Linux kernel's memory barriers. ... I've tried to get rid of the concept of memory accesses appearing on the bus; ... barring implicit enforcement by the CPU. ...
    (Linux-Kernel)
  • Oops in 2.6.28-rc9 and -rc8 -- mtrr issues / e1000e
    ... Bios 1.04beta did show correct memory sizing in dmidecode, ... I hope this is as simple as me doing something glaringly wrong in the kernel ... DMI present. ... CPU: L2 cache: 6144K ...
    (Linux-Kernel)
  • Re: read vs. mmap (or io vs. page faults)
    ... not fit in main memory, and there are overheads related to the heuristics ... But because the CPU is underutilized, ... reasonably sized user buffer). ... You have to measure the actual overhead to see what the actual cost is. ...
    (freebsd-questions)