From owner-freebsd-chromium@FreeBSD.ORG Mon Jan 14 21:52:23 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EDBC5100 for ; Mon, 14 Jan 2013 21:52:23 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id D836AD9E for ; Mon, 14 Jan 2013 21:52:23 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id r0ELqFwG059918; Mon, 14 Jan 2013 13:52:16 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <50F47E0F.9070900@rawbw.com> Date: Mon, 14 Jan 2013 13:52:15 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Jonathan Chen Subject: Re: Oddness with latest chromium References: <50F3B4EF.6090206@chen.org.nz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2013 21:52:24 -0000 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