Bug 204423 - www/chromium: 46.0.2490.80 won't start
Summary: www/chromium: 46.0.2490.80 won't start
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: i386 Any
: --- Affects Some People
Assignee: freebsd-chromium (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-10 08:47 UTC by Alexander Klein
Modified: 2018-01-13 00:50 UTC (History)
4 users (show)

See Also:
bugzilla: maintainer-feedback? (chromium)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Klein 2015-11-10 08:47:09 UTC
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.
Comment 1 dh 2015-11-19 09:06:06 UTC
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)
Comment 2 Heather 2015-11-26 08:09:53 UTC
Same issue for me
Comment 3 dh 2015-12-10 17:54:31 UTC
It seems that the issue is fixed in the chromium version 47.0.2526.73 (available in both ports and pkg).
Comment 4 Alexander Klein 2015-12-11 08:54:07 UTC
47.0.2526.73 from the "quarterly" repo doesn't work for me, either, sorry.
Comment 5 Walter Schwarzenfeld freebsd_triage 2018-01-12 22:57:53 UTC
We have version 61.0.3163.100. This is overcome by events.