Chromium uses 100% of a core, hangs on exit

Latest Chromium
Code: 
root@kg-core1# pv chrom*
[Reading data from pkg(8) ... - 729 packages found - done]
chromium-45.0.2454.101  =  up-to-date with port
also uses 100% of two cores on exit. Still on FreeBSD 9.3-stable:
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
In case this information is useful to those trying to get Chromium to work properly on FreeBSD.
 
I'm not following you. What isn't new information? That a new version of Chromium (still) doesn't work on FreeBSD 9.3-stable?
 
IIRC, there was a change made to the kernel in 11-CURRENT that worked around the issue with Chromium but did not actually fix the problem (Chromium) itself. The change made to to kernel was MFC'd to 10-STABLE before 10.2-RELEASE was released which then included the change. It was not MFC'd to 9.3-STABLE however and won't be for reasons I can't remember at this time. So, from what I understand, Chromium still technically has this issue on all branches. It's just worked around on 10.2-RELEASE and up through a change in the kernel.
 
Well, I decided to test this. So I installed a fresh virtual machine in VirtualBox, with FreeBSD 10.2-release:
Code: 
root@p1# uname -a
FreeBSD p1.kg4.no 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 19:31:38 UTC 2015
  root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386
(actually, I cheated - I just downloaded the official virtual image). The machine has 1 vCPU and (currently) 2560 MB RAM.
I installed the necessary packages to get Xorg LXDE up, and then Chromium:
Code: 
root@p1# pv chrom*
[Reading data from pkg(8) ... - 217 packages found - done]
chromium-45.0.2454.101  =  up-to-date with port
and the only thing running on this machine now (apart from Xorg and LXDE) is Chromium and a couple of xterms.
Anyone want to guess what load it is at?
Code: 
root@p1# date;uptime
Thu Oct 15 23:56:55 CEST 2015
11:56PM  up 48 mins, 6 users, load averages: 2.11, 2.41, 2.79
Additionally, I get frequent "Ahw, snap" messages when trying bookmarks, links or even reloading pages in Chromium.
And this in /var/log/messages:
Code: 
Oct 15 23:26:30 p1 su: tingo to root on /dev/pts/3
Oct 15 23:28:23 p1 kernel: pid 868 (chrome), uid 1001: exited on signal 11
Oct 15 23:29:57 p1 kernel: pid 1226 (chrome), uid 1001: exited on signal 11
Oct 15 23:31:28 p1 kernel: pid 1238 (chrome), uid 1001: exited on signal 11
Oct 15 23:31:36 p1 kernel: pid 1255 (chrome), uid 1001: exited on signal 11
Oct 15 23:31:44 p1 kernel: pid 1257 (chrome), uid 1001: exited on signal 11
Oct 15 23:31:54 p1 kernel: pid 1260 (chrome), uid 1001: exited on signal 11
Oct 15 23:32:04 p1 kernel: pid 1263 (chrome), uid 1001: exited on signal 11
Oct 15 23:34:57 p1 kernel: pid 953 (chrome), uid 1001: exited on signal 11
Oct 15 23:37:32 p1 kernel: pid 929 (chrome), uid 1001: exited on signal 11
No, I'm not impressed.
 
Well, here's mine on a year and a half old machine:

Code: 
8:40PM up 13:43, 9 users, load averages: 0.15, 0.16, 0.11

The "Aw, snap" stuff happens to me occasionally so, yes, the port maintainers can't seem to get that fixed cause it's been there for a couple of weeks.
 
You must log in or register to reply here.
Back
Top