Use IMMEDIATE_CRASH() instead of CRASH() directly

third_party/WebKit/Source/platform/wtf/Assertions.h

Index: third_party/WebKit/Source/platform/wtf/Assertions.h
diff --git a/third_party/WebKit/Source/platform/wtf/Assertions.h b/third_party/WebKit/Source/platform/wtf/Assertions.h
index 33e2b7a1308489583c7ab9162a5d48baaa3d1684..e89a7cd605c9b0b75721f9f21b61bea43d7d1c1b 100644
--- a/third_party/WebKit/Source/platform/wtf/Assertions.h
+++ b/third_party/WebKit/Source/platform/wtf/Assertions.h
@@ -109,17 +109,6 @@ class WTF_EXPORT ScopedLogger {
 
 }  // namespace WTF
 
-// CRASH() - Raises a fatal error resulting in program termination and
-// triggering either the debugger or the crash reporter.
-//
-// Use CRASH() in response to known, unrecoverable errors like out-of-memory.
-// Macro is enabled in both debug and release mode.
-// To test for unknown errors and verify assumptions, use ASSERT instead, to
-// avoid impacting performance in release builds.
-#ifndef CRASH
-#define CRASH() IMMEDIATE_CRASH()
-#endif
-
 #define DCHECK_AT(assertion, file, line)                            \
   LAZY_STREAM(logging::LogMessage(file, line, #assertion).stream(), \
               DCHECK_IS_ON() ? !(assertion) : false)