Blink-in-JS: Allow a stackoverflow error thrown by private scripts

Source/bindings/core/v8/PrivateScriptRunner.cpp

Index: Source/bindings/core/v8/PrivateScriptRunner.cpp
diff --git a/Source/bindings/core/v8/PrivateScriptRunner.cpp b/Source/bindings/core/v8/PrivateScriptRunner.cpp
index 04ac688e9e1e0375e228fbfc013d2cfb2f17f8c2..1295dbfe00062bb7261278c57f5d951d27ad9c57 100644
--- a/Source/bindings/core/v8/PrivateScriptRunner.cpp
+++ b/Source/bindings/core/v8/PrivateScriptRunner.cpp
@@ -254,6 +254,16 @@ void PrivateScriptRunner::rethrowExceptionInPrivateScript(v8::Isolate* isolate,
         return;
     }
 
+    // Standard JS errors thrown by a private script are treated as real errors

[vivekg, 2014/09/09 02:28:36]

Just out-of-curiosity, seems that RangeError is not a defined standard but
within blink/chrome. I just stumbled upon this interesting discussion here [1].

Based on this, I have below two questions:

a. Is there any plan either in ECMAScript6 or ESCMScriptX to make these as
standard exceptions? 
b. Do we need to also handle the out-of-memory case gracefully in the private
scripts? 

[1]
http://esdiscuss.org/topic/standardizing-out-of-memory-and-stack-depth-exceed...

+    // of the private script and crash the renderer, except for a stack overflow
+    // error. A stack overflow error can happen in a valid private script
+    // if user's script can create a recursion that involves the private script.
+    if (exceptionName == "RangeError" && messageString.contains("Maximum call stack size exceeded")) {
+        exceptionState.throwDOMException(V8RangeError, messageString);
+        exceptionState.throwIfNeeded();
+        return;
+    }
+
     fprintf(stderr, "Private script error: %s was thrown.\n", exceptionName.utf8().data());
     dumpV8Message(tryCatchMessage);
     RELEASE_ASSERT_NOT_REACHED();