Issue 121624 in chromium: Slow tab switching
chro...@googlecode.com
Owner: ----
Labels: OS-Linux Area-Undefined Type-Bug Pri-2
New issue 121624 by wra...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
Chrome Version : 19.0.1084.1
OS Version: Debian Unstable
When I switch to another tab, whether by opening a new tab or switching to
an existing one, there is a pause of several seconds before the tab is
displayed and reponsive. This also applies to opening new tabs in
background. This seems to be reproduced with an empty profile too, but
apparently only after I open some sites with complex markup. So, steps to
reproduce:
1. Run Chrome with -user-data-dir=tmp/foo
2. Switch between two initial tabs, open NTP, open google.com: everything
is smooth.
3. Open plus.google.com, try switching and opening NTP: switching to the G+
tab is noticeably slower, opening NTP is too.
4. Open cnn.com, try the same, also try opening some link in a background
tab: everything is even slower, especially opening NTP or switching to it.
I tried the same in Iceweasel 10 and it switches between tabs instantly.
UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/536.5 (KHTML,
like Gecko) Chrome/19.0.1084.1 Safari/536.5
chro...@googlecode.com
Comment #3 on issue 121624 by Dame...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
I'm having the same problem too. I'm testing with 19.0.1084.9 on 64-bit
Debian Unstable + nvidia with their 295.33 driver.
I don't know exactly when it started, but it appears to have been an update
in the 18.X series that first exhibited some weird performance opening and
switching tabs. I thought it must have been a driver issue, so I tried
downgrading my nvidia driver and switching between the stable, beta, and
unstable branches of google chrome. None of the changes I made appears to
make any difference.
chro...@googlecode.com
Comment #4 on issue 121624 by Dame...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
System information if related:
System: Host: damentz64 Kernel: 3.2.0-13.dmz.2-liquorix-amd64 x86_64 (64
bit)
Desktop: KDE 4.7.4 Distro: Linux Mint Debian Edition
Machine: System: Sony (portable) product: VPCCW27FX version: C603UM4E
Mobo: Sony model: VAIO Bios: American Megatrends version:
R0170Y7 date: 05/14/2010
CPU: Dual core Intel Core i5 CPU M 520 (-HT-MCP-) clocked at 2400.00
MHz
Graphics: Card: NVIDIA GT216 [GeForce GT 330M] X.Org: 1.11.4 driver:
nvidia Resolution: 3520...@50.0hz
GLX Renderer: GeForce GT 330M/PCIe/SSE2 GLX Version: 3.3.0
NVIDIA 295.33
Network: Card-1: Marvell 88E8057 PCI-E Gigabit Ethernet Controller
driver: sky2
Card-2: Atheros AR9285 Wireless Network Adapter (PCI-Express)
driver: ath9k
Drives: HDD Total Size: 766.6GB (66.0% used)
Info: Processes: 223 Uptime: 22:28 Memory: 2630.2/7973.3MB Client:
Shell inxi: 1.7.31
chro...@googlecode.com
Comment #5 on issue 121624 by laurent....@clarisys.fr: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
I have the same problem, same system/XOrg driver, but I found something
interresting.
If you disable gtk3 font Antialiasing, the problem vanished.
If you set ANtialiasing to Grayscale instead of RGBA, the problem vanished
too.
Same problem with google-chrome-unstable_19.0.1084.9-r130290_i386.deb
gtk3 libs:
ii libgdu-gtk0
3.0.2-2 GTK+ standard dialog library for libgdu
ii libgtk-3-0:i386
3.2.3-1 GTK+ graphical user interface library
ii libgtk-3-bin
3.2.3-1 programs for the GTK+ graphical user
interface library
ii libgtk-3-common
3.2.3-1 common files for the GTK+ graphical user
interface library
ii libgtk-3-dev
3.2.3-1 development files for the GTK+ library
I also found the same problem on amd64 system.
chro...@googlecode.com
Comment #6 on issue 121624 by laurent....@clarisys.fr: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
Also, it's needed to disable WebGL in chrome://flags
chro...@googlecode.com
Comment #10 on issue 121624 by wra...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
The same with 19.0.1084.15-r130829
chro...@googlecode.com
Comment #11 on issue 121624 by jko...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
Yup, disabling WebGL doesn't help.
This is a dupe of #121289.
chro...@googlecode.com
Comment #12 on issue 121624 by blooda...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
Solution foud ! (see
http://linux.derkeiler.com/Mailing-Lists/Debian/2012-04/msg01078.html)
Pinning libcairo to version 1.10.2-7 when doing the upgrade solves the
problem: it's libcairo 1.12.0-2.
chro...@googlecode.com
Comment #13 on issue 121624 by jko...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
Pinning libcairo to version 1.10.x is just a workaround, not a solution.
According to the cairo bug tracker, NVidia presumably has fixed the bug in
their drivers, and it's now pending a release.
chro...@googlecode.com
Comment #14 on issue 121624 by infinity...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
Exactly same problem here, both with Google Chrome and Chromium. Debian
Sid. Downgrading libcairo makes the tab work properly again.
chro...@googlecode.com
Comment #15 on issue 121624 by infinity...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
BTW, binary nvidia drivers.
chro...@googlecode.com
Comment #16 on issue 121624 by stu...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
This solved it for me:
[test@phat]$ nvidia-settings -a InitialPixmapPlacement=0
I'm on Debian Sid, Nvidia binary drivers, Chrome. Found the tip here:
https://wiki.archlinux.org/index.php/NVIDIA#Bad_performance.2C_e.g._slow_repaints_when_switching_tabs_in_Chrome
chro...@googlecode.com
Comment #17 on issue 121624 by tej.ry...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
Stu's fix worked for me as well. Thanks! Debian Sid, Nvidia binaries,
Chromium, both packaged.
chro...@googlecode.com
Comment #18 on issue 121624 by jager...@jagerman.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
The "fix" in comment 16 indeed fixes the tab switching in Chrome, but it
makes many other drawing operations, such as terminal output in
gnome-terminal, considerably slower. i.e. it's not a fix, just a barely
tolerable workaround.
chro...@googlecode.com
Comment #19 on issue 121624 by aleks.cl...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
comment 16 fixied. rxvt is still plenty fast, even when playing videos in
mplayer's ascii mode :)
chro...@googlecode.com
Comment #20 on issue 121624 by mprz...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
Hit by this bug. As comment 18 said, the InitialPixmapPlacement=0 fixes
Chrome redraws but everything else becomes awfully slow it's simply
unusable (try the scrolling speed of find / at a terminal, for example).
Debian Sid; nvidia-glx 302.11-1 from experimental still hit by the bug.
libcairo2 1.12.2-2; cannot go back to 1.10 as it's out of the repos.
google-chrome-stable 19.0.1084.52-r138391.
Is there a better workaround?
chro...@googlecode.com
Comment #21 on issue 121624 by mprz...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
I found a better workaround: to manually obtain and unpack libcairo 1.10
and make Chrome use it. Still a hack, but less dirty than pinning your
whole system to libcairo 1.10.
chro...@googlecode.com
Comment #22 on issue 121624 by mprz...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
Hit by this bug. As comment 18 said, the InitialPixmapPlacement=0 fixes
Chrome redraws but everything else becomes awfully slow it's simply
unusable (try the scrolling speed of find / at a terminal, for example).
http://www.g0hl1n.net/node/17
chro...@googlecode.com
Comment #23 on issue 121624 by wra...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
The current driver bug is tracked at
https://bugs.freedesktop.org/show_bug.cgi?id=49534
chro...@googlecode.com
Comment #24 on issue 121624 by jarnverm...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
I found out what the problem is. Apparently version 1.10 of libcairo2 had a
patch to disable server side gradients. This patch was not applied to the
1.12 package in the Debian repos (but is applied in the Ubuntu version). I
tried the Ubuntu version which bricked my system, but you could extract the
patch from the Ubuntu source and apply it to the Debian source before you
build it. Here's a description:
"debian/patches/server_side_gradients.patch: - don't use server side
gradients, most drivers don't handle those and are really slow, should
workaround performances issues for ati and nouveau"
Can not confirm that it works, but it worked for others.
chro...@googlecode.com
Comment #25 on issue 121624 by huug...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
You can get older versions of libcairo2 here:
http://snapshot.debian.org/package/cairo/1.10.2-7/#libcairo2_1.10.2-7
HTH
Hugo
chro...@googlecode.com
Comment #26 on issue 121624 by scott.f....@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
Downgrading libcairo did the trick... Chrome was so slow I thought my
computer was dying.
chro...@googlecode.com
Comment #27 on issue 121624 by jarnverm...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
For a permanent fix that does not involve downgrading libcairo2, look here:
http://forums.debian.net/viewtopic.php?f=6&t=80382
chro...@googlecode.com
Comment #29 on issue 121624 by huug...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
But it is easier to pin libcairo2 to the older version than it is to
recompile it. That gets errors:
/sda7/hda10/backup.files/fromhd/home/hugo/libcairo2-1.12.2-1.build/cairo-1.12.2/src/cairo-xlib-source.c:373:2:
error: unknown
type name 'XLinearGradient'
chro...@googlecode.com
Comment #30 on issue 121624 by scott.f....@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
I was able to source libcairo2 1.12 and use the patch in the instructions
provided by the user in comment 27 and created the following AMD64 deb
package, which is also attached. This worked for me! Thanks!
http://tt6.net/libcairo2_1.12.2-2_amd64.deb
Attachments:
libcairo2_1.12.2-2_amd64.deb 890 KB
chro...@googlecode.com
Comment #31 on issue 121624 by scott.f....@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
And the 32bit patched libcairo2 1.12.2, for anyone who wants it:
http://tt6.net/libcairo2_1.12.2-2_i386.deb
or attached.
Attachments:
libcairo2_1.12.2-2_i386.deb 921 KB
chro...@googlecode.com
Comment #32 on issue 121624 by jfdu...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
Comment 30 & 31, best solutions so far.
Using LMDE 64 bit.
chro...@googlecode.com
Comment #35 on issue 121624 by msrchan...@chromium.org: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
@wrar42,
Could you please update Chrome version to latest Stable: 28.0.1500.72 and
update the performance.
Thanks in advance.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
chro...@googlecode.com
Comment #36 on issue 121624 by wra...@gmail.com: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
It was fixed (in chrome or in Debian) some time ago.
chro...@googlecode.com
Status: WontFix
Cc: tkonch...@chromium.org
Labels: -Needs-Feedback
Comment #37 on issue 121624 by tkonch...@chromium.org: Slow tab switching
http://code.google.com/p/chromium/issues/detail?id=121624
As per comment #36, we are closing the issue. Please feel free to file a
new issue if you come across similar issue again.