Reviewers: Mads Ager,

Message:
Mads,

may you have a look?

Description:
Make OutOfMemory exception thrown from JS call into FatalProcessOutOfMemory as
well.

That unifies the behaviour with CALL_HEAP_FUNCTION macro.

BUG=v8:1165

Please review this at http://codereview.chromium.org/6528050/

SVN Base: https://v8.googlecode.com/svn/branches/bleeding_edge

Affected files:
  M src/execution.cc


Index: src/execution.cc
diff --git a/src/execution.cc b/src/execution.cc
index f484d8d9b819af699e25786c8b66b8167441afe1..de8f0a4661544e5fb6ac9aa7c9467ea4afb4a459 100644
--- a/src/execution.cc
+++ b/src/execution.cc
@@ -106,6 +106,11 @@ static Handle<Object> Invoke(bool construct,
   ASSERT(*has_pending_exception == Top::has_pending_exception());
   if (*has_pending_exception) {
     Top::ReportPendingMessages();
+    if (Top::pending_exception() == Failure::OutOfMemoryException()) {
+      if (!HandleScopeImplementer::instance()->ignore_out_of_memory()) {
+        V8::FatalProcessOutOfMemory("JS", true);
+      }
+    }
     return Handle<Object>();
   } else {
     Top::clear_pending_message();


--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev

Reply via email to