Resolution: Cannot Reproduce
Affects Version/s: None
Fix Version/s: None
The dreaded sequel to
HARMONY-222. While the one line fix for that prevents the test suite bringing about a rather undignified exit to the VM it doesn't really address the bigger picture of how to cope with user code that marks files as delete-on-exit and also makes use of the System.runFinalizersOnExit() method. Of course the latter method is deprecated but it won't stop some people from adopting it in their code.
I will attach a test case for dropping into tests/api/java/io/FileTest.java together with some minor tweaks to the build.xml and hyproperties.xml files in modules/luni/make/common that will enable this new test to run. A new support class will also be needed to help run part of the test in a separate VM.
My suggested fix for this is an update to one class in icu4jni-3.4.jar. I think that we are OK customising that jar for Harmony.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|970d 11h 17m||1||Tim Ellison||19/Nov/08 12:38|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Cannot Reproduce [ 5 ]|
|Assignee||Tim Ellison [ tellison ]|
|Summary||Using java.io.File.deleteOnExit() and System.runFinalizersOnExit(true) in the same application causes crash on exit.||[classlib][luni] Using java.io.File.deleteOnExit() and System.runFinalizersOnExit(true) in the same application causes crash on exit.|
|Attachment||Support_DeleteOnExitWithRunFinalizersOnExitTest.java [ 12324559 ]|