Chromium uses 100% of a core, hangs on exit

T

tingo

Chromium 43.0.2357.130 fixed the problem with crashes in Settings. But there is still problems:
If I start Chromium and then quit it after a short time (say 5 - 10 minutes) everything is well. If I wait longer, a Chrome process will stick around after quitting Chromium, and it will use 100% of a cpu core. I can kill it via kill -QUIT ... but then of course it core dumps.
What can we do to find this problem so it can be fixed?
 
I don't have this problem myself in either HEAD or 10-STABLE. Does this happen for you with an empty profile and/or no extensions installed?
 
protocelt said:
I don't have this problem myself in either HEAD or 10-STABLE. Does this happen for you with an empty profile and/or no extensions installed?
Click to expand...
I know how to test with no extensions, and will do so. How do I test with an empty profile (and get my profile back afterwards)?
 
Just rename your configuration directory to something else, restart the browser, test and rename the directory back again when your done after deleting the newly created directory. mv ~/.config/chromium ~/.config/chromium_bak
 
Ok, with an empty profile and without extensions - it still hangs on exit, the hanging process using 100% of a cpu core:
Code: 
tingo@kg-core1$ pgrep -lf chrome
90005 chrome:
90003 /bin/sh /usr/local/bin/chrome
process id of the "100%" process is 90005 in this case.
This on:
Code: 
tingo@kg-core1$ uname -a
FreeBSD kg-core1.kg4.no 9.3-STABLE FreeBSD 9.3-STABLE #0 r273918: Fri Oct 31 22:52:44 CET 2014
  root@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64
 
I don't have any idea what is causing it but I don't have any machines running 9.3-*. I also took a look quick and don't see any PRs filed resembling this issue. Since drhowarddrfine also mentioned he has this issue also on 9.3-* and possibly others, could you possibly file a PR for this?
 
Same problem for me.
I have wiped out my ~/.config/chromium settings folder and still have one chrome process that loop at 100% CPU time.
Have to quit chrome and kill the looping process every time !
my version : 10.1-STABLE amd64
 
Interestingly it appears to behave nicely if I remove the settings folder and I don't sign in with my Google account...
 
Same problem here on 10.0-RELEASE-p2 amd64.

Trying out www/chromium for the first time here after pkg decided to wipe www/firefox from my system. It appears to work if no plugins or extensions are loaded. Seriously this is a problem. Do I really need to switch back to ports to have a web browser on FreeBSD?
 
Perhaps there should be a stable and development packages in this case?

For users, particularly new users, it reflects poorly on FreeBSD if there isn't a working web browser that can be installed.
 
All the browsers you can install on any other OS can be installed on FreeBSD, including chromium which I use all day, every day. Ports of third party software, including chromium, have nothing directly to do with FreeBSD the OS.
 
FYI there's a related PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201543

"This bug is triggered *before* r272566 - not after. the commit in question fixed the bug which was triggering this failure."

Maybe they mean the following commit to base: https://svnweb.freebsd.org/base?view=revision&revision=272566

So now it's either www/chromium gets a q&d patch, or you upgrade your system now.

I am going to upgrade my 10.1-RELEASE to 10.2-BETA2 with freebsd-update and see if it fixes the problem. I will post an update after I've upgraded, rebooted and tested www/chromium.
 
rabfulton said:
Perhaps there should be a stable and development packages in this case?

For users, particularly new users, it reflects poorly on FreeBSD if there isn't a working web browser that can be installed.
Click to expand...

There's plenty other browsers: https://www.freebsd.org/doc/handbook/desktop-browsers.html

I've had similar problems with software even in Windows. These problems are temporal, and the short term solutions is always 1) fix the problem or 2) try another piece of software

Otherwise one just gotta wait until the problem is fixed in system or in the software.
 
I can now confirm that upgrading to 10.2-BETA2 fixes the high CPU usage problem with www/chromium

I did as follows

freebsd-update upgrade -r 10.2-BETA2
freebsd-update install


The above upgrades only the kernel, and asks you to reboot into single user mode. If you are a daredevil, you could do freebsd-update install again, but you might get some programs crashing on shutdown. Since I am a gent, I continued as follows:

nextboot -o "-s" -k kernel
shutdown -r now


The nextboot -o "-s" -k kernel command instructs loader to boot the upgraded kernel into single user mode once. The reboot after that would boot normally. Then, after I got into single user mode I did the following:

mount -o rw /
freebsd-update install
shutdown -r now


After that, my rig happily booted 10.2-BETA2.

I started my VNCServer, and www/chromium in it, and now chrome no longer exhausts CPU.

Problem solved as far as I am concerned. I am not concerned about the stability of 10.2-BETA2, even if it is a beta release. I've never had any stability problems with beta releases, ever. Only problems I've ever run into where minor regressions, but those were always fixed in due time.

I suppose the people who cannot do this are
- those who have to keep the rig running because it is a production server of some kind
- people who do not have time to do a system upgrade; the single user upgrade of userland can take some time, if your rig is slow
 
I'm still on FreeBSD 9.3-stable:
Code: 
tingo@kg-core1$ uname -a
FreeBSD kg-core1.kg4.no 9.3-STABLE FreeBSD 9.3-STABLE #0 r273918: Fri Oct 31 22:52:44 CET 2014  root@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64
I just upgraded Chromium to 44.0.2403.130:
Code: 
root@kg-core1# pv chrom*
[Reading data from pkg(8) ... - 835 packages found - done]
chromium-44.0.2403.130  =  up-to-date with port
and it still hangs on exit, using 100% of a core.
 
Well, it (PR 201543) only says that the bug fix is in 10.2. It does not say that other supported branches of FreeBSD won't get fixed.
 
Last edited by a moderator:
Note that chrome only works fine on 10.2 ATM. If you want to still using chrome on other FreeBSD branches is necessary to downgrade.
 
Upgraded my FreeBSD 9.3-stable to latest:
Code: 
tingo@kg-core1$ uname -a
FreeBSD kg-core1.kg4.no 9.3-STABLE FreeBSD 9.3-STABLE #1 r287724: Sun Sep 13 00:23:47 CEST 2015
  root@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64
and upgraded to latest Chromium
Code: 
root@kg-core1# pv chrom*
[Reading data from pkg(8) ... - 691 packages found - done]
chromium-45.0.2454.85  =  up-to-date with port
and now Chrome manages to use 100% of two cores:
Code: 
root@kg-core1# ps ax -p 32877
  PID TT  STAT  TIME COMMAND
32877 v1  I  14:47.24 chrome:  (chrome)
not impressed.
 
You must log in or register to reply here.
Back
Top