New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 723758 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 722827



Sign in to add a comment

Can't enable DCHECK without disabling this in all fuzzing builds

Project Member Reported by aarya@google.com, May 17 2017

Issue description

We use a ton of release builds with memory instrumented tools. After you last enabled it, it just broke everything on ClusterFuzz. Reason being we don't expect startup crashes with simple tests, so existing more important crash testcases just start getting closed because they will start crashing on completely unrelated stacks.

We need to add explicit hooks to disable this in fuzzing release builds
All Sanitizer Builds (ASAN, MSAN, UBSAN, UBSAN VPTR, CFI, TSAN)
SYZYASAN builds

 

Comment 1 by gab@chromium.org, May 25 2017

Are all of these builds using static (non-component) builds?
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 17 2017

Labels: Hotlist-Google

Comment 3 by gab@chromium.org, Mar 19 2018

Status: Fixed (was: Assigned)
This was strongly noted in 722827, if we try this again it will be based on is_component_build not !is_official_build

Sign in to add a comment