[kepler-dev] [Bug 5484] Module Manager GUI can fail to close and quit parent process

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5484

--- Comment #2 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2011-09-23 12:37:45 PDT ---
I've done further testing trying to replicate one particular form of this bug
on a p4 3ghz 1gb RAM WinXP box. When using the MM GUI from within Kepler 2.3.0,
I see Kepler 2.3.0 and its MM GUI actually do eventually dispose, but it takes
a very long time (~100s).

With 2.2.0 already downloaded, switching to it from within Kepler 2.3.0, it
takes about 25seconds for 2.2.0 to completely start up. Then about 100 seconds
later 2.3.0 and its associated MM GUI closes. I've run this test 3 or 4 times
and get very similar times each test. While doing this I monitor the CPU w/
Windows Task Manager, and see that it is essentially idle during the 100second
wait for 2.3.0 and its MM GUI to close.

Using the exact same test procedure on my mac, I'm unable to replicate -- 2.3.0
and its associated MM GUI close in a couple seconds, before the 2.2.0 splash
comes up. Both XP and OS X are using java 1.6.0_26.

Side question: why are all the MM GUI classes that restart kepler calling
System.exit(1)? These calls occur in areas where kepler is intentionally being
quit without error, why not use exit(0)?

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.