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. On Wed, May 16, 2012 at 11:15 PM, Conrad J. Sabatier <conr...@cox.net> wrote: > For the last week or so, I've been unable to run chrome. Any attempt > to start it up will cause the system either to freeze up or reboot. > > To make matters worse, no trace of what's happening is anywhere to be > found. Nothing in any log files. The system doesn't drop into the > kernel debugger, either. It's either a hard freeze or sudden reboot. > > I've tried rebuilding the chromium port, with both clang and gcc 4.6, > to no avail. I've also updated the system sources several times this > week and remade world/kernel. Nothing seems to help. > > I'm totally stumped as to how to determine what's going on here. Any > suggestions as to how to obtain some useful info? > > Thanks! > > -- > Conrad J. Sabatier > conr...@cox.net > _______________________________________________ > freebsd-chrom...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscr...@freebsd.org" _______________________________________________ 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"
