I've spent some time looking at this, and I'm still unable to reproduce this failure locally or by running the equivalent try bot (linux-blink-heap-verification-try).

Other than enable_blink_heap_verification=true, are there any other special flags I should be using when building locally to replicate this build? 

gn args from https://logs.chromium.org/v/?s=chromium%2Fbuildbucket%2Fcr-buildbucket.appspot.com%2F8950787221187212064%2F%2B%2Fsteps%2Fgenerate_build_files%2F0%2Fstdout

dcheck_always_on = true
enable_blink_heap_verification = true
goma_dir = "/b/swarming/w/ir/cache/goma_client"
is_component_build = false
is_debug = false
strip_absolute_paths_from_debug_symbols = true
use_goma = true

I think it builds using something along the lines of 

python -u /b/swarming/w/ir/.cipd/pkgs/11/0b372dcff1ea986770087adcd0b3f39b3117e8f8/build/scripts/slave/recipe_modules/chromium/resources/ninja_wrapper.py --ninja_info_output /b/swarming/w/ir/tmp/tmpLCrc9H.json --failure_output /b/swarming/w/ir/tmp/tmpeZtBdk -- /b/swarming/w/ir/kitchen-checkout/depot_tools/ninja -w 'dupbuild=err' -C /b/swarming/w/ir/cache/builder/src/out/Release -j 80 base_unittests blink_heap_unittests cacheinvalidation_unittests capture_unittests components_unittests content_browsertests content_unittests crypto_unittests google_apis_unittests gpu_unittests ipc_tests jingle_unittests media_blink_unittests media_unittests midi_unittests net_unittests services_unittests skia_unittests sql_unittests ui_base_unittests unit_tests url_unittests webkit_layout_tests_exparchive webkit_unit_tests wtf_unittests

Maybe building the targets exactly in that order will help

Still no luck, even after using the same gn args, and building the targets in that order. I even tried cleaning the build, building the last successful revision, and then building the first failing revision (this looks like an incremental builder, so I thought this might make a difference).

Is there a way to run a clean build on that builder (non incremental)?

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

commit d5a44c1a71815022d8f5e66023a5778fc68e207c
Author: Adithya Srinivasan <adithyas@chromium.org>
Date: Wed Mar 28 22:44:18 2018

Fix linux-blink-heap-verification build

For some reason, the builder didn't rebuild NodeTest.o after I landed
https://crrev.com/c/980591. The dependencies in BUILD.gn seem okay,
so I'm suspecting it's a clang bug, but I'm not sure and I cannot
reproduce locally.

I'm just adding an include to touch NodeTest.cpp in
this CL, which should force it to get rebuilt and fix the build.

Bug:  826516 
Change-Id: I99f1455e5656890ec958db598cb8eae47899178c
TBR: mlippautz@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/982812
Reviewed-by: Adithya Srinivasan <adithyas@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546633}
[modify] https://crrev.com/d5a44c1a71815022d8f5e66023a5778fc68e207c/third_party/WebKit/Source/core/dom/NodeTest.cpp