InterruptedException after cancel file open dialog - 1.6.0_26

Question

The output from the code that follows is:

java.vendor     Sun Microsystems Inc.
java.version    1.6.0_26
java.runtime.version    1.6.0_26-b03
sun.arch.data.m         


        

Answer 1

The difference I saw between the code in the blog post is the scope of the JFileChooser. In the blog post the object is a local variable within the onClickedButton function. In your example the object is defined at the class level. I assume being a local variable gives the Disposer thread more time to clear the JFileChooser object.

When I made the the file chooser object a local variable in the actionPerformed method block in your example, the exception did not occur. I did test it around ten times, Both running the application through eclipse and through the command line. The exception did not occur.

If the exception still occurs, you can initializing a file chooser object in the constructor of GUI but not assigning it to anything. I assume here it acts as an early initialization and disposal of a heavy weight swing object.

Hope this helps.

Answer 2

Try to add a System.gc() call when done with JFileChooser. I had some problems with file locks that this call fixed.

Answer 3

My output for a slightly altered version of your source (now included as an edit to the question itself) is..

java.vendor     Sun Microsystems Inc.
java.version    1.6.0_29
java.runtime.version    1.6.0_29-b11
sun.arch.data.model     32
os.name         Windows 7
os.version      6.1
os.arch         x86
Input File Selected: install.ini.
Input selection cancelled by user.
Press any key to continue . . .

From your question it seems the important line is:

Input selection cancelled by user.

But after that I see no InterruptedException in the output.

Answer 4

I would say this is a small bug in sun.awt.Disposer.

That class creates the "Java2D Disposer" daemon thread which handles disposing AWT resources of garbage collected objects (mainly AWT windows). Most of the time that thread waits on its reference queue for a new disposable object to be garbage collected. When the thread is interrupted it explicitly prints that exception.

When the JVM is terminated it interrupts all threads. Under some circumstances - which are apparently influenced by the usage of JFileChooser and the subsystems initialized by it - some threads still get a chance to run after this interruption. And in this case an InterruptedException is thrown in the "Java2D Disposer" thread because it was waiting on a lock. It would be better if it ignored that exception during shutdown.

As a workaround, replace

frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);

with

frame.setDefaultCloseOperation(JFrame.DISPOSE_ON_CLOSE);
frame.addWindowListener(new WindowAdapter() {
    @Override
    public void windowClosed(WindowEvent e) {
        PrintStream nullStream = new PrintStream(new OutputStream() {
            public void write(int b) throws IOException {
            }

            public void write(byte b[]) throws IOException {
            }

            public void write(byte b[], int off, int len) throws IOException {
            }
        });
        System.setErr(nullStream);
        System.setOut(nullStream);
        System.exit(0);
    }
});

Answer 5

I had a similar issue. I fixed it following the advice from this thread