Chrome apparently does not seperate UI rendering into different processes as it should.
So when one page becomes blocked for a response (the throbber stops), all my tabs return blank pages.
That problem went away when I enabled GPU composition, but then the in-browser PDF reader that Google insists be included freezes and responds at what I estimate is .0001 frames per second. So then I disabled that, only to find that the GPU composition leaves black box artifacts in one of the page windows. So then I disabled that, only to come back to "Chrome-fucking-twiddles-it's-fucking-thumbs-as-it-waits-for-ONE-tab-to-respond".
I like to open twenty to fifty tabs at a time (like when I browse here).
The worst thing an application can do on my system is jam the UI or be slow to respond. I'd rather have a crashing app than one than makes me tear out my hair because Google Chrome can't differentiate display object models from it's ass or provide a UI that doesn't make me wish for the responsiveness of Adobe Flash.
So when one page becomes blocked for a response (the throbber stops), all my tabs return blank pages.
That problem went away when I enabled GPU composition, but then the in-browser PDF reader that Google insists be included freezes and responds at what I estimate is .0001 frames per second. So then I disabled that, only to find that the GPU composition leaves black box artifacts in one of the page windows. So then I disabled that, only to come back to "Chrome-fucking-twiddles-it's-fucking-thumbs-as-it-waits-for-ONE-tab-to-respond".
I like to open twenty to fifty tabs at a time (like when I browse here).
The worst thing an application can do on my system is jam the UI or be slow to respond. I'd rather have a crashing app than one than makes me tear out my hair because Google Chrome can't differentiate display object models from it's ass or provide a UI that doesn't make me wish for the responsiveness of Adobe Flash.
Slave to the Patriarchy no more
