Received: by 10.68.196.232 with SMTP id ip8mr581375pbc.6.1339204269082;
        Fri, 08 Jun 2012 18:11:09 -0700 (PDT)
X-BeenThere: chromium-b...@chromium.org
Received: by 10.68.212.39 with SMTP id nh7ls6808752pbc.4.gmail; Fri, 08 Jun
 2012 18:11:07 -0700 (PDT)
Received: by 10.68.220.231 with SMTP id pz7mr2209509pbc.110.1339204267631;
        Fri, 08 Jun 2012 18:11:07 -0700 (PDT)
Received: by 10.68.220.231 with SMTP id pz7mr2209506pbc.110.1339204267623;
        Fri, 08 Jun 2012 18:11:07 -0700 (PDT)
Return-Path: <3q6LSTwgODb4glvsqmyqksskpigshi.gsqglvsqmyq-fykwglvsqmyq....@codesite.bounces.google.com>
Received: from mail-pb0-f75.google.com (mail-pb0-f75.google.com [209.85.160.75])
        by mx.google.com with ESMTPS id jo8si5816144pbc.7.2012.06.08.18.11.07
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 08 Jun 2012 18:11:07 -0700 (PDT)
Received-SPF: pass (google.com: domain of 3q6LSTwgODb4glvsqmyqksskpigshi.gsqglvsqmyq-fykwglvsqmyq....@codesite.bounces.google.com designates 209.85.160.75 as permitted sender) client-ip=209.85.160.75;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of 3q6LSTwgODb4glvsqmyqksskpigshi.gsqglvsqmyq-fykwglvsqmyq....@codesite.bounces.google.com designates 209.85.160.75 as permitted sender) smtp.mail=3q6LSTwgODb4glvsqmyqksskpigshi.gsqglvsqmyq-fykwglvsqmyq....@codesite.bounces.google.com
Received: by pbbrr13 with SMTP id rr13so182123pbb.2
        for <chromium-b...@chromium.org>; Fri, 08 Jun 2012 18:11:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.219.170 with SMTP id pp10mr620460pbc.1.1339204267551; Fri,
 08 Jun 2012 18:11:07 -0700 (PDT)
Reply-To: codesite-nore...@google.com
X-Generated-By: Google Code
X-GoogleCode-Project: chromium
X-GoogleCode-Issue-Id: 118149
References: <36-1824057202445553401-15803150459751700841-chromium=googlecode.com@googlecode.com>
 <0-1824057202445553401-15803150459751700841-chromium=googlecode.com@googlecode.com>
In-Reply-To: <36-1824057202445553401-15803150459751700841-chromium=googlecode.com@googlecode.com>
Message-ID: <37-1824057202445553401-15803150459751700841-chromium=googlecode....@googlecode.com>
Date: Sat, 09 Jun 2012 01:11:07 +0000
Subject: Re: Issue 118149 in chromium: Page loads then immediately disappears
 -- ERROR:gles2_cmd_decoder.cc(4725) in Console
From: chrom...@googlecode.com
To: chromium-b...@chromium.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes


Comment #37 on issue 118149 by jdub...@gmail.com: Page loads then  
immediately disappears -- ERROR:gles2_cmd_decoder.cc(4725) in Console
http://code.google.com/p/chromium/issues/detail?id=118149

Indeed I had had threaded compositing enabled when I tried "GPU compositing  
on all pages". Since then I enabled GPU compositing, and disabled threaded  
compositing, and reproduced the bug. At first, everything seemed fine, and  
now I am in a state in which I cannot even get http://www.google.com to  
appear in a new tab. I did restart the browser each time after changing any  
setting.

Oddly, if I hit command-option-J (for script debugging) the page is  
actually shown, after having appeared totally blank.