Fix BlobBytesConsumer state assumption on cancellation

third_party/WebKit/Source/modules/fetch/BlobBytesConsumer.cpp

Index: third_party/WebKit/Source/modules/fetch/BlobBytesConsumer.cpp
diff --git a/third_party/WebKit/Source/modules/fetch/BlobBytesConsumer.cpp b/third_party/WebKit/Source/modules/fetch/BlobBytesConsumer.cpp
index ee586c0253242c7113c9b2fe9329df08afa18f6c..250b8270773cc130dcd9083094c29671643feae5 100644
--- a/third_party/WebKit/Source/modules/fetch/BlobBytesConsumer.cpp
+++ b/third_party/WebKit/Source/modules/fetch/BlobBytesConsumer.cpp
@@ -231,13 +231,7 @@ void BlobBytesConsumer::didFinishLoading(unsigned long identifier,
 
 void BlobBytesConsumer::didFail(const ResourceError& e) {
   if (e.isCancellation()) {
-    // |m_loader| can be canceled when
-    //  - this object explicitly cancels it, or
-    //  - the global context is shutting down.
-    // In the first case, |m_state| should be Closed.
-    if (getExecutionContext() && !getExecutionContext()->isContextDestroyed())
-      DCHECK_EQ(PublicState::Closed, m_state);
-    if (m_state == PublicState::Closed)
+    if (m_state != PublicState::ReadableOrWaiting)
       return;
   }
   DCHECK_EQ(PublicState::ReadableOrWaiting, m_state);