Replace boolean return value SharedBuffer::getAsBytes with DCHECK

third_party/WebKit/Source/core/xmlhttprequest/XMLHttpRequest.cpp

Index: third_party/WebKit/Source/core/xmlhttprequest/XMLHttpRequest.cpp
diff --git a/third_party/WebKit/Source/core/xmlhttprequest/XMLHttpRequest.cpp b/third_party/WebKit/Source/core/xmlhttprequest/XMLHttpRequest.cpp
index 87c5d6516dd2acdf6ad322a64c0ed535a6193948..b1cfcda0d899874c95516ab076cb42da7ba92c4f 100644
--- a/third_party/WebKit/Source/core/xmlhttprequest/XMLHttpRequest.cpp
+++ b/third_party/WebKit/Source/core/xmlhttprequest/XMLHttpRequest.cpp
@@ -391,7 +391,7 @@ DOMArrayBuffer* XMLHttpRequest::responseArrayBuffer() {
         // m_binaryResponseBuilder failed to allocate an ArrayBuffer.
         // We need to crash the renderer since there's no way defined in
         // the spec to tell this to the user.
-        CRASH();
+        OOM_CRASH();

[tyoshino (SeeGerritForStatus), 2016/11/28 05:29:33]

This comment was correct when it was written. But now, the condition in the
if-clause is not returning success/fail of buffer allocation. Allocation happens
on L387.

https://chromium.googlesource.com/chromium/src/+/b2da98fba6daaf142757f3aa1b94...
When this comment was written, SharedBuffer::getAsArrayBuffer() contained a
buffer allocation call which is invocation of
ArrayBuffer::createUninitialized(). ArrayBuffer::createUninitialized() returned
nullptr on allocation failure.

https://chromium.googlesource.com/chromium/src/+/3dfbd2ef9d62505887e29f276625...
This change moved the DOMArrayBuffer creation out of getAsArrayBuffer(), but
https://chromium.googlesource.com/chromium/src/+/3dfbd2ef9d62505887e29f276625...
create() was returning nullptr when the given buffer is nullptr. So, it was
still correct.

https://chromium.googlesource.com/chromium/src/+/612660c50e4ae437e379b299fa75...
This change removed the nullptr check code from DOMArrayBuffer. The commit log
is suggesting that we should use createOrNull() when we want to get nullptr on
allocation failure, but it wasn't changed to do so.

https://chromium.googlesource.com/chromium/src/+/4a7f1339c93c0b19ec75779d93a0...
And, on the same day, this change refactored allocation and serialization into
two separate lines.

So, we should:
- call ArrayBuffer::createOrNull(). If it returns nullptr, call OOM_CRASH().
- call DOMArrayBuffer* create(PassRefPtr<WTF::ArrayBuffer> buffer) with the
created ArrayBuffer.
- when getAsBytes() fails, CRASH() as it's bad but not allocation failure.

       }
       m_responseArrayBuffer = buffer;
       m_binaryResponseBuilder.clear();