You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexei Zakharov (JIRA)" <ji...@apache.org> on 2006/12/07 16:40:25 UTC
[jira] Updated: (HARMONY-248) [classlib][luni] Using
java.io.File.deleteOnExit() and System.runFinalizersOnExit(true) in the
same application causes crash on exit.
[ http://issues.apache.org/jira/browse/HARMONY-248?page=all ]
Alexei Zakharov updated HARMONY-248:
------------------------------------
Summary: [classlib][luni] Using java.io.File.deleteOnExit() and System.runFinalizersOnExit(true) in the same application causes crash on exit. (was: 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.
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-248
> URL: http://issues.apache.org/jira/browse/HARMONY-248
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Environment: WinXP
> Reporter: George Harley
> Attachments: Harmony-248.txt, icu4jni-3.4.jar, Support_DeleteOnExitWithRunFinalizersOnExitTest.java
>
>
> 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.
> Best regards,
> George
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira