[jira] Closed: (HARMONY-248) [classlib][luni] Using java.io.File.deleteOnExit() and System.runFinalizersOnExit(true) in the same application causes crash on exit.

["Tim Ellison (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HARMONY-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Ellison closed HARMONY-248.
-------------------------------

    Resolution: Cannot Reproduce
      Assignee: Tim Ellison

This old issue cannot be reproduced on M8...

    public static void main(String[] args) throws IOException {
        File f = File.createTempFile("foo", "bar");
        f.deleteOnExit();
        System.runFinalizersOnExit(true);
        System.out.println("works for me");
    }

> [classlib][luni] Using java.io.File.deleteOnExit() and System.runFinalizersOnExit(true) in the same application causes crash on exit.
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-248
>                 URL: https://issues.apache.org/jira/browse/HARMONY-248
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>         Environment: WinXP
>            Reporter: George Harley
>            Assignee: Tim Ellison
>         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.
-
You can reply to this email to add a comment to the issue online.