Chrome stopped working for me after I upgraded to 46.0.2490.80. When started from the command line, it will spawn two processes, one of which is in state kqread consuming 0% CPU, while the other is in state uwait consuming 100% CPU. The last working version seems to be 45.0.2454.101, although this fails quite often showing an "Oh no!" message in its tabs. I don't know whether it really makes a difference, but use ctwm as my window manager.
I'm also experiencing same behaviour with 46.0.2490.80 and 46.0.2490.86. Chromium processes are running but no windows are opened. On startup I get one message: [13694:438129664:1119/105828:ERROR:nss_util.cc(853)] After loading Root Certs, loaded==false: NSS error code: -8018 When using truss on one of the chrome processes I only get spammed with following output: __sysctl(0x7fffffffcf40,0x4,0x7fffffffcf60,0x7fffffffcf58,0x0,0x0) = 202 (0xca)
Same issue for me
It seems that the issue is fixed in the chromium version 47.0.2526.73 (available in both ports and pkg).
47.0.2526.73 from the "quarterly" repo doesn't work for me, either, sorry.
We have version 61.0.3163.100. This is overcome by events.