Sign up ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

Is anyone else finding Chrome/Chromium 15 slow?

My specific situation involves a page of thumbnails (where the thumbnail is actually the full image resized using width= and height= ); clicking the thumbnail makes the full size image appear in an iframe on the same page. With Chrome 14 this was instant, and the machine was immediately available for another click. With Chrome 15, this is still instant, but there then follow several seconds of 100% processor usage by Chrome/Chromium as it does goodness-only-knows-what, rendering the entire machine unusable for that period. Clicking quickly through the thumbnails is therefore no longer possible.

What are the options for reverting to Chrome/Chromium 14 (if it is possible at all)?

I managed to download Chromium 14 before it followed Chrome in updating to 15, but now I am being nagged every day to upgrade it as part of the daily updates. Can I switch that off? Are there any other options?

I'd also like to explore downgrading further, to before Chrome started pointlessly wasting a 3-pixel deep bar at the top of the page on the F11 full-page view...

share|improve this question

1 Answer 1

up vote 3 down vote accepted

Except in Ubuntu 10.04 LTS Lucid Lynx, and in Precise (the development version which will eventually be released as Ubuntu 12.04 LTS Precise Pangolin), the Ubuntu updates to chromium-browser 15 have not yet been released, but are still undergoing testing in -proposed (source: See for details about the different repositories that provide newer versions of software in Ubuntu, and for information about the -proposed repositories.

I would encourage you to search and see if the problem you are having has been reported, and if it hasn't been, to report it. Please make sure to read carefully first. Then, to file the bug, either run "ubuntu-bug chromium-browser" or invoke ubuntu-bug with the PID of the currently running chromium-browser process (this will make sense after you read ReportingBugs). Make sure to describe the problem clearly and fully in your bug report. After filing your bug, you should post about it in bug 881786; if your bug is considered to qualify for a SRU, it might cause the still-proposed versions to be delayed until the problem is fixed.

If you're running Ubuntu 10.10 Maverick Meerkat, Ubuntu 11.04 Natty Narwhal, or Ubuntu 11.10 Oneiric Ocelot, then you can downgrade from chromium-browser 15 to chromium-browser 14, as major version 14 still still available through the -updates repository (or the release repository in Oneiric). You might find that the easiest way to do this is in the Synaptic Package Manager (which itself can be installed in the Software Center--the package is called: synaptic). Or you can use apt-get from the command-line to perform the downgrade; for example, on an Ubuntu 11.10 Oneiric Ocelot system, you could run "sudo apt-get install chromium-browser=14.0.835.202~r103287-0ubuntu1" (without the quotes). See the apt-get manual page for details. If you are running one of these systems, then chromium-browser was upgraded from the -proposed repository, so you can prevent it from being updated further until the version 15 packages have underwent further testing and been released for general use by disabling that software source or, better, by using pinning (as explained in EnableProposed).

If you're running Ubuntu 10.04 LTS Lucid Lynx, or Precise, the above method will not work, but you might still have the .deb package for major version 14 of chromium-browser in your /var/cache/apt/archives folder. If you don't, then you can see if it's still present at It probably is, at least if you act fast, but you should check your /var/log/dpkg.log file to see what the version was on your machine to ensure you get the right one, because if you get the wrong one it could be for a different Ubuntu release, and subtle problems could potentially occur. You should also make sure to get the version for the right architecture, where i386 is for 32-bit Ubuntu systems and amd64 is for 64-bit Ubuntu systems, irrespective of whether your processor is actually manufactured by Intel or AMD. If it's not there, then you could see if it's still on Launchpad by subtituting the old version string (from /var/log/dpkg.log) into the URL (for a 32-bit system) or (for a 64-bit system).

Please note that if you do manually downgrade chromium-browser, you might need to perform a similar procedure to downgrade related packages, i.e., one or more of the following (probably not the -dbg packages, as you likely do not have them installed): chromium-browser-dbg, chromium-browser-inspector, chromium-browser-l10n, chromium-codecs-ffmpeg-dbg, chromium-codecs-ffmpeg-extra-dbg, chromium-codecs-ffmpeg-extra, chromium-codecs-ffmpeg-nonfree-dbg, chromium-codecs-ffmpeg-nonfree, and chromium-codecs-ffmpeg.

Finally, please note that chromium-browser (Chromium) and Google Chrome are separate applications--the instructions in this post apply to Chromium, which is probably easier to downgrade.

If you attempt to follow these procedures and have difficulty, I'd be please to provide additional assistance (please go ahead and post a comment or comments describing the difficulties).

share|improve this answer
I can't see in the faq where to say thankyou, so I'll say thankyou here. Brilliant full answer providing several different solutions, thankyou. I found the .deb in /var/cache/apt/archives for google-chrome 14, so I have installed that, and switched off google updates, and uninstalled chromium. I will try to report the bug, but the etiquette is so complicated - I'll research it tomorrow. Thankyou again. – Michael Hampson Oct 29 '11 at 18:12
I'm glad my answer was helpful. You may want to make a backup of that .deb file, in case you end up cleaning or autocleaning your local packages archives (which could remove it). While I agree that you should familiarize yourself with the bug reporting guidelines before filing a bug, you should also be aware that the community on Launchpad is pretty welcoming to novices (or to people who are not novices, but who are novices when it comes to filing bugs), and pretty tolerant of mistakes, and the system is designed to make it possible to improve bug reports that are initially lacking. – Eliah Kagan Oct 29 '11 at 19:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.