[DrJava] [ drjava-Bugs-1207107 ] DrJava will not die

[SourceForge.net <no...@so...>]

Bugs item #1207107, was opened at 2005-05-23 09:14
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=438935&aid=1207107&group_id=44253

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Makes DrJ unstable
Status: Open
Resolution: None
Priority: 5
Submitted By: Eric E. Allen (eallen)
Assigned to: Nobody/Anonymous (nobody)
Summary: DrJava will not die

Initial Comment:
I tried out the new drjava 20050509 beta on Mac OS X 10.4. I 
wrote some simple code using the Java3D API (which I do not 
believe to be related to my problem) and let the application run idle 
overnight. In the morning, I ran into the anomalous 
"StackOverflowException" that still seems to occur with DrJava 
on OS X after it runs idle long enough (there's a bug report on that 
problem somewhere in the DrJ bug list). Then I tried to quit 
DrJava, and I ran into the following exception:

edu.rice.cs.util.ExitingNotAllowedException: The call to 
System.exit() was not allowed.
	at edu.rice.cs.util.PreventExitSecurityManager.checkExit
(PreventExitSecurityManager.java:161)
	at java.lang.Runtime.exit(Runtime.java:88)
	at java.lang.System.exit(System.java:868)
	at com.apple.eawt.Application$6.run(Application.java:388)
	at java.awt.event.InvocationEvent.dispatch
(InvocationEvent.java:209)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:
461)
	at 
java.awt.EventDispatchThread.pumpOneEventForHierarchy
(EventDispatchThread.java:267)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy
(EventDispatchThread.java:196)
	at java.awt.EventDispatchThread.pumpEvents
(EventDispatchThread.java:190)
	at java.awt.EventDispatchThread.pumpEvents
(EventDispatchThread.java:182)
	at java.awt.EventDispatchThread.run
(EventDispatchThread.java:110)

I had to resort to force quitting the application.

Given that the exception is thrown by a custom security manager, 
I take it that there is something I'm doing that you're trying to 
prevent... Please advise.

Thanks,

-- Eric



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=438935&aid=1207107&group_id=44253