Fix missing HandleScope to prevent local handles to DOMWindow leaking.

src/profile-generator.cc

Index: src/profile-generator.cc
diff --git a/src/profile-generator.cc b/src/profile-generator.cc
index 1a2d005a6feb927f490de53361ad8886a3f041d4..6a31a7c24cca6c2070e621414d4f3dc999b81abf 100644
--- a/src/profile-generator.cc
+++ b/src/profile-generator.cc
@@ -2473,6 +2473,7 @@ void V8HeapExplorer::TagGlobalObjects() {
   Isolate* isolate = Isolate::Current();
   GlobalObjectsEnumerator enumerator;
   isolate->global_handles()->IterateAllRoots(&enumerator);
+  HandleScope scope;

[Erik Corry, 2011/11/14 23:02:50]

Perhaps better to have this in the loop.  As it is now, an unlimited number of
handles is ceated (depending on enumerator.count()).  It is good that they are
destroyed at the end of this function, but it seems even better if they are
destroyed at the end of each loop iteration.

[mnaganov (inactive), 2011/11/15 09:58:27]

The number of global objects is usually limited. But OK, shorting handles lives
even more seems good to me.

[Vitaly Repeshko, 2011/11/15 18:55:59]

This is too late. Global object handles have already been created in
GlobalObjectsEnumerator.

[mnaganov (inactive), 2011/11/15 19:56:18]

A good catch! %)

   Handle<String> document_string =
       isolate->factory()->NewStringFromAscii(CStrVector("document"));
   Handle<String> url_string =