heap: Fix MARKING_AWARE_ANNOTATE_CHANGE_SIZE macro

Based on binary size, the branch in the macro wasn't optimized away on non-asan
builds. This fix manually removes the branch when it's not needed.

Bug: 1099412
Change-Id: I318f02fc7c254db0dc2b5098109734d170138b5e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276279Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Omer Katz <omerkatz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#784411}

third_party/blink/renderer/platform/wtf/vector.h

@@ -79,6 +79,7 @@ class Deque;
 // capacity as accessible. With concurrent marking enabled, annotating size
 // changes could conflict with marking the whole store as accessible, causing
 // a race.
+#if defined(ADDRESS_SANITIZER)
 #define MARKING_AWARE_ANNOTATE_CHANGE_SIZE(Allocator, buffer, capacity,      \
                                            old_size, new_size)               \
   if (Allocator::kIsGarbageCollected && Allocator::IsIncrementalMarking()) { \
@@ -86,6 +87,11 @@ class Deque;
   } else {                                                                   \
     ANNOTATE_CHANGE_SIZE(buffer, capacity, old_size, new_size)               \
   }
+#else
+#define MARKING_AWARE_ANNOTATE_CHANGE_SIZE(Allocator, buffer, capacity, \
+                                           old_size, new_size)          \
+  ANNOTATE_CHANGE_SIZE(buffer, capacity, old_size, new_size)
+#endif  // defined(ADDRESS_SANITIZER)
 
 template <bool needsDestruction, typename T>
 struct VectorDestructor;