Date: Fri, 19 Nov 2010 22:16:09 +0100 From: Oliver Pinter <oliver.pntr@gmail.com> To: Alexander Best <arundel@freebsd.org> Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-current@freebsd.org, "Robert N. M. Watson" <rwatson@freebsd.org>, Garrett Cooper <gcooper@freebsd.org> Subject: Re: www/chromium crashing whole system Message-ID: <AANLkTi=1q11Z_9hNv03oVTCya8UMmz_APSh_sKOCFhN=@mail.gmail.com> In-Reply-To: <20101119152855.GA34603@freebsd.org> References: <20101113122853.GG2392@deviant.kiev.zoral.com.ua> <20101113123846.GA21390@freebsd.org> <20101113124146.GH2392@deviant.kiev.zoral.com.ua> <20101113124758.GA23469@freebsd.org> <alpine.BSF.2.00.1011132206380.12353@fledge.watson.org> <AANLkTim7ZGLFTj_3WZiC9hAsAaOVrz6yhKcMURV%2BsKvu@mail.gmail.com> <alpine.BSF.2.00.1011132212400.12353@fledge.watson.org> <4CDF0F03.10703@freebsd.org> <20101115221924.GA38676@freebsd.org> <EF3468C7-91EB-49ED-9966-88EDF0AF5A08@freebsd.org> <20101119152855.GA34603@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <arundel@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-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=1q11Z_9hNv03oVTCya8UMmz_APSh_sKOCFhN=>