3 ms·

Just took out that tab for me in windows. Seems like something else is probably going on for you.

• laumars 14y ago
  Chromium has been a little dodgy for me lately too. Lots of memory leaks and what not. I've had to kill it's parent process id on a number of occasions (but even then, there's no reason why a browser should take out the whole OS).
  • isalmon 14y ago
    Same here. Google has to do something with all these memory leaks.
    • gcb0 14y ago
      ...Or releasing their iron grip on the repo.
  • atesti 14y ago
    They are also not really visibly working on issues like these: http://code.google.com/p/chromium/issues/detail?id=222558 http://code.google.com/p/chromium/issues/detail?id=222558 http://code.google.com/p/chromium/issues/detail?id=134837 http://code.google.com/p/chromium/issues/detail?id=134837 Basically, each font in each size uses some handles in a renderer. At 10000 handles, the tab renderer dies. They have a font cache but never clear it. When enough render processes together use too many GDI handles, the whole Windows desktop breaks down.