Chrome crashing system (amd64-10.0-CURRENT)

Conrad J. Sabatier conrads at
Thu May 17 23:08:57 UTC 2012

On Thu, 17 May 2012 08:55:49 -0700
Evan Martin <evan at> wrote:

> These kinds of hard locks often point at graphics driver problems, but
> normally Chrome relies on a driver whitelist that likely doesn't
> include any FreeBSD drivers.  Did you perhaps set a flag somewhere to
> bypass a blacklist?
> You could try some command line flags like
> --blacklist-accelerated-compositing
> --blacklist-webgl
> to see if they help.
> (I found those on
> , not
> certain if they do what you need.)
> Another idea is to use strace/ktrace/truss into a log file to see what
> it was doing around the time of dying.

Thanks.  I tried those, and it still locked up.

I finally just moved away ~/.config/chromium, and it started up OK.
Luckily, I was able to restore pretty much everything from my synced

Happy ending.  :-)

Conrad J. Sabatier
conrads at

More information about the freebsd-current mailing list