9
3
Whenever I want to switch to a tab other than the one that is being rendered, Chrome hangs for about 2 seconds before rendering the new tab. This occurs whenever a new tab has to be showed, such as clicking the "New Tab" button, or closing the current tab.
Here's my version information:
Google Chrome 14.0.835.163 (Official Build 101024)
OS:Linux (Ubuntu 11.04)
WebKit 535.1 (branches/chromium/835@94713)
The only extension I use is AdBlock, and disabling it had no effect.
This has only been occurring to me since I updated to the most recent version of Chrome.
Any idea of what's going on?
Have you tried disabling the default "New Tab"-Page? You can do so with the extension "New Tab Redirect".
Try changing it to
about:blank
. Does it make any difference?I'm not sure if I was clear. This happens even if I have two tabs open, say one on www.google.com, and another on www.youtube.com, and I want to switch from one to the other (also, the problem doesn't depend on the content of the tabs: I can have two tabs on about:version, and switching between them causes the delay). – Alex Dias – 2011-09-19T20:31:43.893
As far as I was able to see, there were no bug reports about this problem. Could it be a conflicting application? – Duijf – 2011-09-19T20:45:00.407
Perhaps, even though this occurs also when not much else is running. Just before I updated Chrome (which caused the issue), I installed gcc-4.4, g++-4.4 and their dependencies (giving me two versions of both gcc and g++: 4.4 and 4.5). However, doing this on a live cd didn't cause any problems, so I guess the two installed versions of gcc and g++ aren't what's causing the problem. Also, I just installed Chromium, and the problem does not exist there. – Alex Dias – 2011-09-19T20:52:22.300
Interestingly, this started to happen to me just now when updating to a new version on 2012-04-13. It now happens with stable, unstable and beta builds. I see many other intermittent bug reports on this subject, but no real answers. I'll continue investigations. – Daniel Andersson – 2012-04-13T14:43:59.387
My issue still stands, and I can't find any reasons. I even tried downgrading to a version where I know it did not happen (both Chrome and the Nvidia driver), and it happened there as well. I tried Chromium and it was the same thing. And the bug reports mentioning this at Google seem to be getting no responses. Anyone with an idea of what could be causing it? – Daniel Andersson – 2012-04-28T20:47:03.397