Received: by 10.224.186.17 with SMTP id cq17mr6325438qab.6.1337294657360;
        Thu, 17 May 2012 15:44:17 -0700 (PDT)
X-BeenThere: chromium-b...@chromium.org
Received: by 10.224.33.13 with SMTP id f13ls2595326qad.1.gmail; Thu, 17 May
 2012 15:44:15 -0700 (PDT)
Received: by 10.229.134.194 with SMTP id k2mr4372138qct.42.1337294654952;
        Thu, 17 May 2012 15:44:14 -0700 (PDT)
Received: by 10.229.134.194 with SMTP id k2mr4372137qct.42.1337294654937;
        Thu, 17 May 2012 15:44:14 -0700 (PDT)
Return-Path: <3Pn-1TwgODZU16GDB7JB5DD5A31D23.1DB16GDB7JB-0J5H16GDB7JB....@codesite.bounces.google.com>
Received: from mail-qc0-f204.google.com (mail-qc0-f204.google.com [209.85.216.204])
        by mx.google.com with ESMTPS id w2si3051675qct.129.2012.05.17.15.44.14
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 17 May 2012 15:44:14 -0700 (PDT)
Received-SPF: pass (google.com: domain of 3Pn-1TwgODZU16GDB7JB5DD5A31D23.1DB16GDB7JB-0J5H16GDB7JB....@codesite.bounces.google.com designates 209.85.216.204 as permitted sender) client-ip=209.85.216.204;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of 3Pn-1TwgODZU16GDB7JB5DD5A31D23.1DB16GDB7JB-0J5H16GDB7JB....@codesite.bounces.google.com designates 209.85.216.204 as permitted sender) smtp.mail=3Pn-1TwgODZU16GDB7JB5DD5A31D23.1DB16GDB7JB-0J5H16GDB7JB....@codesite.bounces.google.com
Received: by qcso4 with SMTP id o4so47321qcs.3
        for <chromium-b...@chromium.org>; Thu, 17 May 2012 15:44:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.177.202 with SMTP id bj10mr6304063qab.7.1337294654776;
 Thu, 17 May 2012 15:44:14 -0700 (PDT)
Reply-To: codesite-nore...@google.com
X-Generated-By: Google Code
X-GoogleCode-Project: chromium
X-GoogleCode-Issue-Id: 128422
References: <4-1824057202445553401-6295022383394306207-chromium=googlecode.com@googlecode.com>
 <0-1824057202445553401-6295022383394306207-chromium=googlecode.com@googlecode.com>
In-Reply-To: <4-1824057202445553401-6295022383394306207-chromium=googlecode.com@googlecode.com>
Message-ID: <5-1824057202445553401-6295022383394306207-chromium=googlecode....@googlecode.com>
Date: Thu, 17 May 2012 22:44:14 +0000
Subject: Re: Issue 128422 in chromium: Browser crash in InstantFieldTrial::GetMode
From: chrom...@googlecode.com
To: chromium-b...@chromium.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes


Comment #5 on issue 128422 by sree...@chromium.org: Browser crash in  
InstantFieldTrial::GetMode
http://code.google.com/p/chromium/issues/detail?id=128422

Thanks, Eric. I guess you looked at the second crash (the path through  
InstantController::SetOmniboxBounds, which is what refers to | 
tab_contents_->profile()|). If you would be so nice as to look at the first  
crash as well, that would be very helpful. Because, in the first crash,  
Instant is just passing along the profile pointer it receives from  
browser.cc, so it will be nice to know if the dangling pointer issue is  
specific to Instant or more general.