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

Issue 283024: Prevent multiple threads from executing the DumpDoneCallback handler... (Closed)

Created:
11 years, 2 months ago by cpu_(ooo_6.6-7.5)
Modified:
9 years, 7 months ago
Reviewers:
Nicolas Sylvain
CC:
chromium-reviews_googlegroups.com, kuchhal
Visibility:
Public.

Description

Prevent multiple threads from executing the DumpDoneCallback handler - So respawning the browser is more reliable. BUG=25091 TEST=see bug Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=29364

Patch Set 1 #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+9 lines, -0 lines) Patch
M chrome/app/breakpad_win.cc View 2 chunks +9 lines, -0 lines 2 comments Download

Messages

Total messages: 3 (0 generated)
cpu_(ooo_6.6-7.5)
11 years, 2 months ago (2009-10-16 22:47:31 UTC) #1
Nicolas Sylvain
lgtm http://codereview.chromium.org/283024/diff/1/2 File chrome/app/breakpad_win.cc (right): http://codereview.chromium.org/283024/diff/1/2#newcode152 Line 152: ::Sleep(INFINITE); why not just return false?
11 years, 2 months ago (2009-10-16 22:58:46 UTC) #2
cpu_(ooo_6.6-7.5)
11 years, 2 months ago (2009-10-17 00:54:19 UTC) #3
http://codereview.chromium.org/283024/diff/1/2
File chrome/app/breakpad_win.cc (right):

http://codereview.chromium.org/283024/diff/1/2#newcode152
Line 152: ::Sleep(INFINITE);
On 2009/10/16 22:58:46, Nicolas Sylvain wrote:
> why not just return false?

Because we are in the exception hander still so the first thread to return
causes the process to terminate.

Powered by Google App Engine
This is Rietveld 408576698