[BLUEJ-1371] Using system.exit() in a class may provke BlueJ user JVM unresponsiveness
Tried with BlueJ 5.0.2 Windows (standalone), with a class that contains "System.exit(0)" in its main method. The class content is given below. (Don't know if that makes any difference: the BlueJ terminal is set to wipe at each method call)
To reproduce the bug do the following:
-
right click on the given class to open the menu, and select "new Test()"; do NOT validate the popup, just leave it open
-
right click on the given class to open the menu, and select "void main(String[] args)", and click OK
-
quite quickly soon after step 2, now validate the popup of step 1)
The new object shouldn't be created. If it did, repeat this procedure until the object doesn't get created. When this happens, no object can further be created, the main method doesn't produce anything. BlueJ isn't crashed as such it looks like nothing can be done on the user JVM.
Class: public class Test { public Test() { System.out.println("One.. "); System.out.println("Two.. "); System.out.println("Three.. "); System.out.println("Four.. "); System.out.println("Five.. "); System.out.println("Six.. "); System.out.println("Seven.. "); }
public static void main(String[] args) { Test app = new Test(); System.exit(0); } }
Issue metadata
- Issue type: Bug
- Priority: Medium