[oilpan]: Ensure context destroyed is propagated to parent.

With my previous fix for some of the websocket crashes I didn't propagated the fact that the context was destroyed to the base class. This resulted in some cases where we called unobserveContext with where the lifecycle context was actually dead, crashing since further down the stack since it ended up calling on zapped memory. This change should fix that.

R=ager@chromium.org, erik.corry@gmail.com, haraken@chromium.org, oilpan-reviews@chromium.org, tkent@chromium.org, vegorov@chromium.org, zerny@chromium.org
BUG=

Review URL: https://codereview.chromium.org/407493003

git-svn-id: svn://svn.chromium.org/blink/trunk@178435 bbb929c8-8fbe-4397-9dbb-9b2b20218538

third_party/WebKit/Source/modules/websockets/NewWebSocketChannelImpl.h

@@ -162,6 +162,7 @@ private:
         ASSERT(!m_handle);
         ASSERT(!m_client);
         ASSERT(!m_identifier);
+        ContextLifecycleObserver::contextDestroyed();
 #else
         // This object must be destroyed before the context.
         ASSERT_NOT_REACHED();