LinkedList exceptions after failed export

[Robert Leach]

USE CASE: WHAT DO YOU WANT TO DO?

Select new options and try an export over that failed.

STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)

This issue can be reproduced in 2 ways. The first is to intentionally encounter a java heap space error. On my system, you can get this by:

1. Open the large_1kx1k_average.cdt file (which is actually a 1k by 6k matrix)
2. Type command-e to export
3. Select row labels (yes)
4. Click export
5. Select a file name that does not exist as a filename already (i.e. don't replace an existing file)
6. Click save
7. Click OK in the error window
8. Then just click around anywhere in the export dialog and watch the exceptions get thrown in the console

I may end up (partially) fixing the above in my work on issue 443, so the exception may only occur when you click the export button again. Note that exceptions will not occur if the export file exists on the system. If you cannot make the java heap space error happen, you can make the bug occur by:

1. Open a large file that takes a few seconds to export (e.g. the large_6kx6k file)
2. Type command-e to export
3. Click export
4. Select a file name that does not exist as a filename already (i.e. don't replace an existing file)
5. Click save
6. Quickly click cancel during the export
7. Delete the file on the file system
8. Repeat from step 1

CURRENT BEHAVIOR

LinkedList exceptions get thrown as long as the exported file does not exist in the file system and they get thrown by clicking on or off of the export dialog window (e.g. on a different app's window). In my work on issue 443, I'm going to mitigate this by checking the actionPerformed source (line 171 of ExportDialogController) "public void actionPerformed(ActionEvent arg0) {". However, the exception should still occur the next time you click export.

EXPECTED BEHAVIOR

No exceptions.

DEVELOPERS ONLY SECTION

SUGGESTED CHANGE (Pseudocode optional)

I suspect that the exported file name is being saved in a linked list and that the connection of the ExportListener is somehow getting corrupted. Not sure exactly, but that's where I would start.

FILES AFFECTED (where the changes will be implemented) - developers only

ExportDialogController ExportDialog

LEVEL OF EFFORT - developers only

medium

COMMENTS