Bug 202150

Summary: www/chromium: chromium window does not open, process hangs at 100%
Product: Ports & Packages Reporter: Tony Narlock <tony>
Component: Individual Port(s)Assignee: freebsd-chromium mailing list <chromium>
Status: Closed FIXED    
Severity: Affects Only Me CC: bkarp, mail, z3tbl4
Priority: --- Flags: bugzilla: maintainer-feedback? (chromium)
Version: Latest   
Hardware: Any   
OS: Any   

Description Tony Narlock 2015-08-07 06:36:43 UTC
Maybe related: bug #201543. Process still runs at 100%, but no window opens.

Anything else in mind I can try to squeeze info out of this?

$ freebsd-version -ku; uname -apKU
10.1-RELEASE-p17
10.1-RELEASE-p16
FreeBSD z600 10.1-RELEASE-p17 FreeBSD 10.1-RELEASE-p17 #1: Fri Aug  7 00:06:34 CDT 2015     root@z600:/usr/obj/usr/src/sys/MYKERNEL  amd64 amd64 1001000 1001000


tony at z600 in ~ 
$ pkg info chromium
chromium-44.0.2403.125
Name           : chromium
Version        : 44.0.2403.125
Installed on   : Thu Aug  6 05:30:05 CDT 2015
Origin         : www/chromium
Architecture   : freebsd:10:x86:64
Prefix         : /usr/local
Categories     : www
Licenses       : MPL and LGPL21 and BSD3CLAUSE
Maintainer     : chromium@FreeBSD.org
WWW            : http://www.chromium.org/Home
Comment        : Google web browser based on WebKit
Options        :
	CODECS         : on
	DEBUG          : off
	GCONF          : on
	KERBEROS       : on
	PULSEAUDIO     : off
	TEST           : off


# chrome --enable-logging --v=9

[6512:379176960:0807/013017:VERBOSE1:multi_log_ct_verifier.cc(76)] Adding CT log: Google 'Pilot' log
[6512:379176960:0807/013017:VERBOSE1:multi_log_ct_verifier.cc(76)] Adding CT log: Google 'Aviator' log
[6512:379176960:0807/013017:VERBOSE1:multi_log_ct_verifier.cc(76)] Adding CT log: DigiCert Log Server
[6512:379176960:0807/013017:VERBOSE1:multi_log_ct_verifier.cc(76)] Adding CT log: Google 'Rocketeer' log
[6512:379176960:0807/013017:VERBOSE1:multi_log_ct_verifier.cc(76)] Adding CT log: Certly.IO log
[6512:379176960:0807/013017:VERBOSE1:multi_log_ct_verifier.cc(76)] Adding CT log: Izenpe log
[6512:377512960:0807/013017:VERBOSE1:pref_proxy_config_tracker_impl.cc(215)] 0x8168ca500: set chrome proxy config service to 0x8168ca680
[6512:377512960:0807/013017:VERBOSE1:pref_proxy_config_tracker_impl.cc(353)] 0x8168ca500: Done pushing proxy to UpdateProxyConfig
[6513:377512960:0807/013018:VERBOSE1:child_thread_impl.cc(310)] Mojo is disabled on child



$ ps aux  | grep chrome
tony       6711  100.0  0.5  452848  59952  0  I+    1:30AM   0:54.61 chrome: --enable-logging --v=9 (chrome)
tony       6709    0.0  0.0   17072   2732  0  I+    1:30AM   0:00.00 /bin/sh /usr/local/bin/chrome --enable-logging --v=9
tony       6712    0.0  0.6  423056  80012  0  I+    1:30AM   0:00.11 chrome: --type=gpu-process --channel=6711.0.1210476548 --enable-logging --v=9 --suppor...


(different PID, same situation, was trying again)

➜  toolkit  ./execsnoop
  UID    PID   PPID ARGS
 1001   5278   2421 /bin/sh /usr/local/bin/chrome
 1001   5279   5278 /sbin/sysctl -n kern.ipc.shm_allow_removed
 1001   5280   5278 /usr/local/share/chromium/chrome
dtrace: error on enabled probe ID 2 (ID 60857: syscall:freebsd:execve:return): invalid address (0x4) in action #7 at DIF offset 136
 1001   5282   5280 chrome: 
 1001   5282   5280 chrome: 
 1001   5282   5280 chrome: 
 1001   5282   5280 chrome: 
 1001   5282   5280 chrome: 
 1001   5282   5280 chrome: 
 1001   5282   5280 chrome: 
 1001   5282   5280 chrome: 
 1001   5282   5280 chrome: 
 1001   5282   5280 chrome: 
 1001   5282   5280 /bin/sh /usr/local/bin/xdg-settings check default-web-browser chromium-browser.desktop
 1001   5283   5282 dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetNameOwner string:org.gnome.SessionManager
 1001   5284   5282 xprop -root _DT_SAVE_MODE
 1001   5285   5282 grep  = \"xfce4\"$
 1001   5287   5286 grep -q ^WebBrowser= /usr/local/etc/xdg/xfce4/helpers.rc
 1001   5289   5288 grep ^WebBrowser= /usr/local/etc/xdg/xfce4/helpers.rc
 1001   5290   5288 cut -d= -f 2-
 1001   5291   5280 chrome: 
 1001   5291   5280 chrome: 
 1001   5291   5280 chrome: 
 1001   5291   5280 chrome: 
 1001   5291   5280 chrome: 
 1001   5291   5280 chrome: 
 1001   5291   5280 chrome: 
 1001   5291   5280 which xdg-settings



➜  toolkit  ./procsystime -a -p 6711
Tracing... Hit Ctrl-C to end...
dtrace: 140179 dynamic variable drops with non-empty dirty list
dtrace: 134892 dynamic variable drops with non-empty dirty list
dtrace: 110129 dynamic variable drops with non-empty dirty list
dtrace: 105691 dynamic variable drops with non-empty dirty list
dtrace: 106451 dynamic variable drops with non-empty dirty list
dtrace: 106079 dynamic variable drops with non-empty dirty list
dtrace: 106683 dynamic variable drops with non-empty dirty list
dtrace: 117387 dynamic variable drops with non-empty dirty list
^C
dtrace: 136633 dynamic variable drops with non-empty dirty list

Elapsed Times for PID 6711,

         SYSCALL          TIME (ns)
        __sysctl         1824050237
        _umtx_op         6000041966
          TOTAL:         7824092203

CPU Times for PID 6711,

         SYSCALL          TIME (ns)
        _umtx_op               4788
        __sysctl         1548786004
          TOTAL:         1548790792

Syscall Counts for PID 6711,

         SYSCALL              COUNT
        _umtx_op                  1
        __sysctl            1124647
          TOTAL:            1124648
Comment 1 bkarp 2015-08-08 21:10:58 UTC
Just a quick confirmation that I observe the identical behavior--no window opens, 100% CPU on one core--on my machine, too:

% freebsd-version -ku
10.1-RELEASE-p16
10.1-RELEASE-p17

And this is building chromium 44.0.2403.125.
Comment 2 mail 2015-08-10 12:41:06 UTC
Same here.

# freebsd-version -ku
10.1-RELEASE-p16
10.1-RELEASE-p17

# pkg info chromium
chromium-44.0.2403.130
Name           : chromium
Version        : 44.0.2403.130
Installed on   : Mon Aug 10 11:17:59 CEST 2015
Origin         : www/chromium
Architecture   : freebsd:10:x86:64
Prefix         : /usr/local
Categories     : www
Licenses       : MPL and LGPL21 and BSD3CLAUSE
Maintainer     : chromium@FreeBSD.org
WWW            : http://www.chromium.org/Home
Comment        : Google web browser based on WebKit
Options        :
	CODECS         : on
	DEBUG          : off
	GCONF          : on
	KERBEROS       : off
	PULSEAUDIO     : off
	TEST           : off
Comment 3 z3tbl4 2015-08-17 09:53:55 UTC
portupgrade -fRP chromium
Comment 4 Tony Narlock 2015-09-09 18:25:50 UTC
I'm able to run chromium fine now.

Note, I had to initially start chromium like this:

chrome --no-extensions

To get it to run initially.

I'm closing this issue.

# pkg info chromium
chromium-44.0.2403.155
Name           : chromium
Version        : 44.0.2403.155
Installed on   : Sun Sep  6 17:41:36 CDT 2015
Origin         : www/chromium
Architecture   : freebsd:11:x86:64
Prefix         : /usr/local
Categories     : www
Licenses       : MPL and LGPL21 and BSD3CLAUSE
Maintainer     : chromium@FreeBSD.org
WWW            : http://www.chromium.org/Home
Comment        : Google web browser based on WebKit
Options        :
        CODECS         : on
        DEBUG          : off
        DRIVER         : off
        GCONF          : on
        KERBEROS       : on
        PULSEAUDIO     : off
        TEST           : off