1. 42
  1.  

  2. 6

    Now if only chrome could run without consuming 35% cpu while it isn’t even in focus…

    1. 13

      Browsers: ubiquitous, unavoidable, and atrocious no matter which flavor you choose.

      1. 5

        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.

      2. 0

        dwm ftw! :D