New issue
Advanced search Search tips

Issue 654813 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Oct 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chromium takes 150% cpu after page load

Reported by riverf...@free.fr, Oct 11 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/52.0.2743.116 Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. Boot Ubuntu Mate on a machine with an intel card
2. Open https://www.facebook.com/U2
3. Wait until page is loaded

What is the expected behavior?
cpu usage goes down after page finishes loading.

What went wrong?
Chromium continues to take 150% cpu after page is finished loading. This makes chromium slow and unresponsive until the tab is closed.

Did this work before? N/A 

Chrome version: 53.0.2785  Channel: stable
OS Version: Ubuntu Mate 16.04
Flash Version: 

Hi,

I tried known workarounds for intel cards like disabling gpu acceleration and disabling bootloader graphics, VESA framebuffer and PAT but nothing worked so far.

This is not something new, Chromium 49 does this too (and some older versions also iirc) and this affects both Ubuntu 14.04 and 16.04.

Issue seems hardware related:
I can replicate the issue on 2 laptops with integrated Intel  cards (GMA 3150 with i915 driver for instance) but not on another one with a radeon card.

To replicate the issue in Ubuntu Mate 16.04 LiveCD just boot, apt-get update and apt-get install chromium-browser from it.

I tried different LiveCDs, strangely enough only non-gnome/unity desktops seem affected:

Affected: Xubuntu, Lubunt, Ubuntu Mate, Kubuntu (all 16.04)
Not Affected: Ubuntu, Ubuntu Gnome (16.04 also)

This is what I have so far, if I can provide more info just let me know.
 

Comment 1 by riverf...@free.fr, Oct 12 2016

Stack traces of the process when it happens show Blink and V3, I guess this indicates Chromium is stuck in a repaint loop ?

Wondering why it works in regular Ubuntu with Unity...
At least it's not like the drivers are different there:
If I kill Unity in the Ubuntu LiveCD and bring up a minimal desktop environment with just metacity as wm as in:
  http://askubuntu.com/questions/833868/way-to-run-ubuntu-livecd-without-unity
and try chromium there, now it fails to release cpu.

I guess either Chromium behaves differently under Unity, or Unity does something which bypasses the issue ...

Labels: TE-Hardware-Dependency
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 16 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment