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

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) {