From owner-freebsd-chromium@FreeBSD.ORG Thu Feb 5 05:16:36 2015 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8A94176E for ; Thu, 5 Feb 2015 05:16:36 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 770A02C7 for ; Thu, 5 Feb 2015 05:16:36 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t155GaXH070570 for ; Thu, 5 Feb 2015 05:16:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: maintainer-feedback requested: [Bug 197342] www/chromium often shows corrupted pages Date: Thu, 05 Feb 2015 05:16:36 +0000 X-Bugzilla-Type: request Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2015 05:16:36 -0000 emz@norma.perm.ru has reassigned Bugzilla Automation = 's request for maintainer-feedback to chromium@FreeBSD.org: Bug 197342: www/chromium often shows corrupted pages https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D197342 --- Description --- www/chromium often shows corrupted pages, like here: http://static.enaza.ru/userupload/gyazo/3440665460a77084c77cf02d68ae.png This started about some time ago (may be about a year). First I thought that this is a problem with dependencies/memory/something else. But since that I ruled out all of these problems. Plus, this happens only on first opening of the page - when F5 is pressed, the page reloads and displays just fine (oft= en F5 need to be hit multiple times). I'm using the=20 chromium-38.0.2125.101_2 on a=20 FreeBSD bsdrookie.norma.com. 10.1-BETA1 FreeBSD 10.1-BETA1 #0 r271608: Mon = Sep 15 14:14:36 YEKT 2014 emz@bsdrookie.norma.com.:/usr/obj/usr/src/sys/GENER= IC amd64 but this isn't really the version. I've seen such artifacts from the chromi= um 33.x at least.=20 I'm using Firefox as my primary browser, and everything is fine in it. --- Comment #1 from Bugzilla Automation --- Auto-assigned to maintainer chromium@FreeBSD.org=