Update Memory.RendererUsed only after Blink is initialized
commitfdeac26a1bf4babb74961fc08967825c9f45a67f
authorkouhei@chromium.org <kouhei@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 10 Jul 2014 12:52:51 +0000 (10 12:52 +0000)
committerkouhei@chromium.org <kouhei@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 10 Jul 2014 12:52:51 +0000 (10 12:52 +0000)
treedd6acc6b135f3cfd3e714f1ecbbfee620b2a2872
parentad66db1afee6c9be75a7de80901fd774b6cf027b
Update Memory.RendererUsed only after Blink is initialized

Yak shaving to land https://codereview.chromium.org/380533003/

Before the patch, |MemoryObserver| called |GetMemoryUsageKB()| without
any check, which is only valid after webkit is initialized.
GetMemoryUsageKB queries |v8::Isolate::GetCurrent()| internally, but the
query fails on DCHECK on debug builds.

This patch moves the |MemoryObserver| instantiation inside |RenderThreadImpl::EnsureWebKitInitialized|.

BUG=None

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282321 0039d316-1c4b-4281-b951-d872f2087c98
content/renderer/render_thread_impl.cc
content/renderer/render_thread_impl.h
content/renderer/renderer_main.cc