New issue
Advanced search Search tips

Issue 687326 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

calling CHECK should result in EXCEPTION_BREAKPOINT exit code from process

Project Member Reported by wfh@chromium.org, Jan 31 2017

Issue description

Chrome Version: Chrome 52+
OS: Windows

What steps will reproduce the problem?
(1) Call CHECK() from a renderer.
(2) Look in chrome://histograms
(3)

What is the expected result?

An entry in CrashExitCodes.Renderer in bucket 2147483645 (STATUS_BREAKPOINT)

What happens instead?

An entry in CrashExitCodes.Renderer in bucket 1073741819 (STATUS_ACCESS_VIOLATION)

Please use labels and text to provide additional information.

It seems that https://codereview.chromium.org/1982123002/ changed this behavior, maybe?

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


 
Cc: scottmg@chromium.org

Comment 2 by wfh@chromium.org, Feb 6 2017

as part of https://codereview.chromium.org/2648423006/ I found a good place to add regression tests for this type of behavior, so once scott's CL lands, I'll go and add a browser test and a magic URL to verify this actually sticks.
Project Member

Comment 3 by bugdroid1@chromium.org, Feb 15 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a17c8db528cadca9eef98ce03b0910700735722e

commit a17c8db528cadca9eef98ce03b0910700735722e
Author: scottmg <scottmg@chromium.org>
Date: Wed Feb 15 21:35:49 2017

Make CHECK int 3 on Windows, rather than crash

Not being able to distinguish intentional crashes (CHECK) from unintentional ones (other access violations) in terms of exit codes reduces the amount of signal we have in stability metrics.

R=wfh@chromium.org
BUG= 664209 , 687326 

Review-Url: https://codereview.chromium.org/2676483002
Cr-Commit-Position: refs/heads/master@{#450809}

[modify] https://crrev.com/a17c8db528cadca9eef98ce03b0910700735722e/base/logging.h
[modify] https://crrev.com/a17c8db528cadca9eef98ce03b0910700735722e/base/logging_unittest.cc

Labels: Merge-Request-57
Owner: scottmg@chromium.org
Status: Started (was: Untriaged)
Project Member

Comment 5 by sheriffbot@chromium.org, Feb 16 2017

Labels: -Merge-Request-57 Hotlist-Merge-Approved Merge-Approved-57
Your change meets the bar and is auto-approved for M57. Please go ahead and merge the CL to branch 2987 manually. Please contact milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), ketakid@(cros), govind@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 6 by bugdroid1@chromium.org, Feb 16 2017

Labels: -merge-approved-57 merge-merged-2987
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/225319af95b483fc525e08149b4d1d64524dd9c4

commit 225319af95b483fc525e08149b4d1d64524dd9c4
Author: Scott Graham <scottmg@chromium.org>
Date: Thu Feb 16 22:14:16 2017

Make CHECK int 3 on Windows, rather than crash

Not being able to distinguish intentional crashes (CHECK) from unintentional ones (other access violations) in terms of exit codes reduces the amount of signal we have in stability metrics.

R=wfh@chromium.org
BUG= 664209 , 687326 

Review-Url: https://codereview.chromium.org/2676483002
Cr-Commit-Position: refs/heads/master@{#450809}
(cherry picked from commit a17c8db528cadca9eef98ce03b0910700735722e)

Review-Url: https://codereview.chromium.org/2695833008 .
Cr-Commit-Position: refs/branch-heads/2987@{#564}
Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}

[modify] https://crrev.com/225319af95b483fc525e08149b4d1d64524dd9c4/base/logging.h
[modify] https://crrev.com/225319af95b483fc525e08149b4d1d64524dd9c4/base/logging_unittest.cc

Status: Fixed (was: Started)

Sign in to add a comment