Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(273)

Issue 10453020: fix crash when double-deleting a profile (Closed)

Created:
8 years, 7 months ago by Evan Stade
Modified:
8 years, 6 months ago
Reviewers:
sail
CC:
chromium-reviews, arv (Not doing code reviews), binji
Visibility:
Public.

Description

fix crash when double-deleting a profile this fixes both the UI (so it's impossible to trigger the crash) and skirts around the crash itself (which could potentially still be triggered via a UI race, i.e. if the user clicks fast enough). BUG=129651 (maybe? not sure I understand that bug but this has a very similar stack signature) TEST=create second profile. open delete dialog for that profile (don't delete yet). Go to profile 2 window, open settings. Open delete dialog for profile 2. Confirm delete of profile 2 on profile 2 window. Notice that the delete confirmation dialog in profile 1's window has now closed on its own. Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=139419

Patch Set 1 #

Total comments: 3
Unified diffs Side-by-side diffs Delta from patch set Stats (+8 lines, -2 lines) Patch
M chrome/browser/profiles/profile_info_cache.cc View 1 chunk +6 lines, -2 lines 3 comments Download
M chrome/browser/resources/options2/browser_options.js View 1 chunk +2 lines, -0 lines 0 comments Download

Messages

Total messages: 5 (0 generated)
Evan Stade
8 years, 7 months ago (2012-05-25 01:22:53 UTC) #1
Miranda Callahan
On 2012/05/25 01:22:53, Evan Stade wrote: Haven't touched this code in quite a while; sending ...
8 years, 7 months ago (2012-05-25 15:29:59 UTC) #2
sail
LGTM Sorry for the slow turn around. binji: FYI http://codereview.chromium.org/10453020/diff/1/chrome/browser/profiles/profile_info_cache.cc File chrome/browser/profiles/profile_info_cache.cc (right): http://codereview.chromium.org/10453020/diff/1/chrome/browser/profiles/profile_info_cache.cc#newcode230 chrome/browser/profiles/profile_info_cache.cc:230: ...
8 years, 6 months ago (2012-05-28 18:45:07 UTC) #3
Evan Stade
http://codereview.chromium.org/10453020/diff/1/chrome/browser/profiles/profile_info_cache.cc File chrome/browser/profiles/profile_info_cache.cc (right): http://codereview.chromium.org/10453020/diff/1/chrome/browser/profiles/profile_info_cache.cc#newcode230 chrome/browser/profiles/profile_info_cache.cc:230: NOTREACHED(); On 2012/05/28 18:45:07, sail wrote: > Hm... I ...
8 years, 6 months ago (2012-05-29 18:12:13 UTC) #4
sail
8 years, 6 months ago (2012-05-29 18:38:21 UTC) #5
http://codereview.chromium.org/10453020/diff/1/chrome/browser/profiles/profil...
File chrome/browser/profiles/profile_info_cache.cc (right):

http://codereview.chromium.org/10453020/diff/1/chrome/browser/profiles/profil...
chrome/browser/profiles/profile_info_cache.cc:230: NOTREACHED();
On 2012/05/29 18:12:13, Evan Stade wrote:
> On 2012/05/28 18:45:07, sail wrote:
> > Hm... I don't think this NOTREACHED() is going to be hit.
> > 
> > All of the getters go through ProfileInfoCache::GetInfoForProfileAtIndex()
> which
> > already has a DCHECK().
> 
> this seems safer in case the code ever changes, so I'd rather leave it unless
> you feel strongly.

makes sense!

Powered by Google App Engine
This is Rietveld 408576698