You are not logged in.

#1 2012-05-12 07:42:24

pilotkeller
Member
From: Canada
Registered: 2011-12-22
Posts: 513
Website

[Solved] Chromium - Overusing CPU

Today I wanted to take a look into Chromium. So I:

  1. pacman grabbed it

  2. went setting by setting configuring it

  3. signed into my google accounts

  4. found all simmiler addons from firefox (List below)

  5. Configured every addon

  6. checked out the about:flags section

  7. enabled the "Uber Page" (Tested both with and without this)

  8. launched htop

  9. put on mplayer with my favorite podcasts

  10. then started surfing...

About 1-2 minutes later the entire (more or less (Seems to be a render thread (Meaning the UI reacts to input, but the chrome (UI at the top of the browser, not the browser's name) becomes wonky and the pages fails to respond))) browser lagged to a hault and htop showed that /bin/lib/chromium/chromium had ~120% CPU utilisation. One of the cores is running a solid 100% used and nothing will get the browser going again except a relaunch.

I have tried everything, and even doing nothing in roughly the same time will acheive the same result.

The chromium task manager shows 0 CPU usage among all "Pages" then jumped later to show 104% for the browser.

I tried to view chrome:memory, but it just wouldn't load.

The memory ran essentially at ~400M of memory the entire time and my system has 4G of it, so it's not a memory problem.

dmesg | tail:

[   39.296961] EXT4-fs (sda1): re-mounted. Opts: (null)
[   39.498669] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[   39.580976] Adding 19535036k swap on /dev/sda2.  Priority:-1 extents:1 across:19535036k 
[   40.623737] r8169 0000:03:00.0: eth0: link down
[   40.623748] r8169 0000:03:00.0: eth0: link down
[   40.623926] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   42.972541] r8169 0000:03:00.0: eth0: link up
[   42.972734] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   53.203443] eth0: no IPv6 routers present
[   87.057552] fuse init (API version 7.18)

Extensions:

  • Adblock+

  • Do Not Track

  • Ghostery

  • HTTPS Evereywhere

  • Keep MORE Opt Outs

  • Link Master

  • NotScript

  • TinEye

  • User-Agent Switcher

  • Vimium

  • Web Developer

Just checked my TTY1 fom which I launched X. Seems that the crashing thread is throwing the following error twice on chromium's boot:

...:ERROR:bus.cc(261)] Failed to connect to the bus: Failded to connect to the socket /var/run/dbus/system_bus_socket: No such file or directory

I now tried running it with the --no-sandbox option. Same result.

I now ran:

$pacman -Syyu

so I know I'm up to date. I haven't rebooted since installing chromium, so I will try that after posting and will update this thread if anything changes.

-----------------------------------------------------------------------------
Solution:

Well it seems it was a problem with just the addons. No matter how I played, anything more than 7 would yeild the same thing. Honnestly, Chromium's plugin API is awful. I'll stick with firefox, at least it can run my plugins to tweek the UI to my liking (All 32 of them... UGH).

Last edited by pilotkeller (2012-05-12 16:59:27)

Offline

Board footer

Powered by FluxBB