Replaced deprecated v8 API calls by their non-deprecated counterparts.

chrome/browser/task_manager/task_manager_resource_providers.cc

Index: chrome/browser/task_manager/task_manager_resource_providers.cc
diff --git a/chrome/browser/task_manager/task_manager_resource_providers.cc b/chrome/browser/task_manager/task_manager_resource_providers.cc
index 89c193a1e4b4fd966b46649e1a382d1b3e5a6c57..3179611bafa0f7f641b4333d0f33a1b007a330d0 100644
--- a/chrome/browser/task_manager/task_manager_resource_providers.cc
+++ b/chrome/browser/task_manager/task_manager_resource_providers.cc
@@ -1688,13 +1688,13 @@ bool TaskManagerBrowserProcessResource::ReportsV8MemoryStats() const {
 
 size_t TaskManagerBrowserProcessResource::GetV8MemoryAllocated() const {
   v8::HeapStatistics stats;
-  v8::V8::GetHeapStatistics(&stats);
+  v8::Isolate::GetCurrent()->GetHeapStatistics(&stats);

[jochen (gone - plz use gerrit), 2013/03/04 13:51:25]

in the browser process, the only v8 embedder is the network stack. Should we get
the isolate from the network stack? should the network stack have a method that
returns the total/used heap size for its js vm?

[Sven Panne, 2013/03/04 15:01:46]

I'll add a static method to retrieve heap statistics from the network stack,
this seems cleaner than retrieving its Isolate and use that. It's an
implementation detail if there is a single one or more.

   return stats.total_heap_size();
 }
 
 size_t TaskManagerBrowserProcessResource::GetV8MemoryUsed() const {
   v8::HeapStatistics stats;
-  v8::V8::GetHeapStatistics(&stats);
+  v8::Isolate::GetCurrent()->GetHeapStatistics(&stats);
   return stats.used_heap_size();
 }