can you try disable the chrome sandbox feature? chmod -s chrome-sandbox mv chrome-sandbox chrome-sandbox.disabled_feature
and after this, the problem is still represented? under linux with grsec path, with enabled sandbox, do not started, I know, that is a fully different problem On 11/19/10, Alexander Best <arun...@freebsd.org> wrote: > On Tue Nov 16 10, Robert N. M. Watson wrote: >> >> On 15 Nov 2010, at 22:19, Alexander Best wrote: >> >> > thanks for all your help. i've recently switched to chromium 6.0.472.63 >> > and so far my computer has been very stable. >> > >> > if i experience more lock ups i'll let you know and try to figure out a >> > way to >> > gain access to some more debugging data. >> >> I'd prefer we try to figure out why your system was crashing now -- the >> kernel bug has not gone away just because Chromium is no longer triggering >> it. Working around the bug means someone else gets to run into it later -- >> perhaps when it's 9.0-RELEASE rather than 9-CURRENT... > > "GOOD" news btw: the new chromium port just crashed my system. ;) so the > issue is still there. > > and be issue i mean the code that triggers the crash. > >> >> Robert > -- > a13x > _______________________________________________ > 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" > _______________________________________________ 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"
