Date: Mon, 14 Jan 2013 13:52:15 -0800 From: Yuri <yuri@rawbw.com> To: Jonathan Chen <jonc@chen.org.nz> Cc: freebsd-chromium@freebsd.org Subject: Re: Oddness with latest chromium Message-ID: <50F47E0F.9070900@rawbw.com> In-Reply-To: <CAJuc1zM2d5s1vDH=OrgFXvW%2BGz1R7raNzdAG2fq%2BV4bryCr%2BVw@mail.gmail.com> References: <50F3B4EF.6090206@chen.org.nz> <CANcjpOD0_Sc=ktAKEYie30UzGraNUDbfkxr4rEtFwhZHTj=pXg@mail.gmail.com> <CAJuc1zPH_BSkJoNZ2T53bS=fM7PgU4=XH8f0FU=dhrFeJ5F%2Bqg@mail.gmail.com> <CANcjpOCEEu%2B=wnDyEROczWw-rePcCO4ah1q_9S1yqfLPL6hm3g@mail.gmail.com> <CAJuc1zM2d5s1vDH=OrgFXvW%2BGz1R7raNzdAG2fq%2BV4bryCr%2BVw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/14/2013 13:30, Jonathan Chen wrote: > Ok, that appears to be the key tunable that starts to make everything work > again. I've been using chromium for about an hour now and haven't > encountered any unexpected behaviour so far. This also means that some error condition due to the lack of this tunable setting went unnoticed and chrome was malfunctioning instead of warning about the issue. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50F47E0F.9070900>