On Thu, 17 May 2012 08:55:49 -0700 Evan Martin <e...@chromium.org> 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 > http://peter.sh/experiments/chromium-command-line-switches/ , 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 data. Happy ending. :-) -- Conrad J. Sabatier conr...@cox.net _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
