Now if only chrome could run without consuming 35% cpu while it isn’t even in focus…
Browsers: ubiquitous, unavoidable, and atrocious no matter which flavor you choose.
Heh. Reminds me of this fix: http://marc.info/?l=openbsd-cvs&m=142831194326812&w=2
Every time Firefox got a mouse move event, it would essentially screen grab itself (!) which triggered a buffer grow/shrink loop in the X server, bouncing a pile of memory through mmap/munmap along the way.
dwm ftw! :D