Date: Thu, 17 May 2012 18:08:49 -0500 From: "Conrad J. Sabatier" <conrads@cox.net> To: Evan Martin <evan@chromium.org> Cc: freebsd-chromium@freebsd.org, John Hixson <john@ixsystems.com>, freebsd-current@freebsd.org Subject: Re: Chrome crashing system (amd64-10.0-CURRENT) Message-ID: <20120517180849.72ac2664@serene.no-ip.org> In-Reply-To: <CAFzwtj2bh6YaJ%2BkOY4%2BhrSFOSD=rvNoSziBeg0v6skBbQ1hb7Q@mail.gmail.com> References: <20120517011554.5d16067e@serene.no-ip.org> <CAFzwtj2bh6YaJ%2BkOY4%2BhrSFOSD=rvNoSziBeg0v6skBbQ1hb7Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 17 May 2012 08:55:49 -0700 Evan Martin <evan@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 conrads@cox.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120517180849.72ac2664>