From 48faea2ace6e28eb8d87f19d4d1fed865f602995 Mon Sep 17 00:00:00 2001
From: Michael Bayne <mdb@threerings.net>
Date: Fri, 29 Sep 2006 00:45:58 +0000
Subject: [PATCH] All VirtualMachineErrors seem worthy of fork sticking. Also
 re: my previous checkin, tihs will be a non-issue when we start devoting an
 entire separate JVM to each game (which we will have to do for all games that
 run server code) because then all a game can do is stick a fork in its own
 JVM and render itself unplayable.

git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@4388 542714f4-19e9-0310-aa3c-eee0fc999fb1
---
 .../com/threerings/presents/server/PresentsDObjectMgr.java    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/java/com/threerings/presents/server/PresentsDObjectMgr.java b/src/java/com/threerings/presents/server/PresentsDObjectMgr.java
index 9ea43866d..12c45a95d 100644
--- a/src/java/com/threerings/presents/server/PresentsDObjectMgr.java
+++ b/src/java/com/threerings/presents/server/PresentsDObjectMgr.java
@@ -278,7 +278,7 @@ public class PresentsDObjectMgr
                 processEvent((DEvent)unit);
             }
 
-        } catch (OutOfMemoryError e) {
+        } catch (VirtualMachineError e) {
             handleFatalError(unit, e);
 
         } catch (Throwable t) {
@@ -417,7 +417,7 @@ public class PresentsDObjectMgr
                 target.notifyListeners(event);
             }
 
-        } catch (OutOfMemoryError e) {
+        } catch (VirtualMachineError e) {
             handleFatalError(event, e);
 
         } catch (Throwable t) {