On Thu, May 17, 2012 at 4:08 PM, Conrad J. Sabatier wrote:
> 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.
It's a little surprising to me that a
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-compo
