From owner-freebsd-chromium@freebsd.org Fri Jul 20 20:24:16 2018 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD95B10516DD for ; Fri, 20 Jul 2018 20:24:16 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 508B28BFB1 for ; Fri, 20 Jul 2018 20:24:15 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (x5271625d.dyn.telefonica.de [82.113.98.93]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id w6KKO8ff086004 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 20 Jul 2018 20:24:08 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host x5271625d.dyn.telefonica.de [82.113.98.93] claimed to be ultrabook.yoonka.com Subject: Re: [Bug 212812] www/chromium: tabs "hang" 10% of the time To: freebsd-chromium@freebsd.org References: From: Grzegorz Junka Message-ID: <1532547c-74a1-bb50-8e88-b43e13af7b90@gjunka.com> Date: Fri, 20 Jul 2018 20:24:02 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2018 20:24:16 -0000 On 20/07/2018 19:28, bugzilla-noreply@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812 > > --- Comment #81 from Jan Beich --- > Can someone check if the patch in bug 181741 has any effect? Maybe some hangs > (e.g., cache on high latency storage but not GPU driver bugs) are due to IPC. > > Just a wild guess. > Do you know in which version of Chrome it ended up?