You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "George Harley (JIRA)" <ji...@apache.org> on 2006/03/24 18:21:42 UTC
[jira] Created: (HARMONY-248) Using java.io.File.deleteOnExit() and
System.runFinalizersOnExit(true) in the same application causes crash on
exit.
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
Type: Bug
Components: Classlib
Environment: WinXP
Reporter: George Harley
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
[jira] Updated: (HARMONY-248) Using java.io.File.deleteOnExit() and
System.runFinalizersOnExit(true) in the same application causes crash on
exit.
Posted by "George Harley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-248?page=all ]
George Harley updated HARMONY-248:
----------------------------------
Attachment: icu4jni-3.4.jar
Patched version of icu4jni-3.4.jar. Replace the one in jre/lib/boot with this and the VM crash at shutdown time should (hopefully) be gone.
I guess that we should be maintaining patch source as well somewhere in the repository.
Best regards,
George
> 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
> Type: Bug
> Components: Classlib
> Environment: WinXP
> Reporter: George Harley
> Attachments: Harmony-248.txt, Support_DeleteOnExitWithRunFinalizersOnExitTest.java, icu4jni-3.4.jar
>
> 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
[jira] Updated: (HARMONY-248) Using java.io.File.deleteOnExit() and
System.runFinalizersOnExit(true) in the same application causes crash on
exit.
Posted by "George Harley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-248?page=all ]
George Harley updated HARMONY-248:
----------------------------------
Attachment: Harmony-248.txt
Test case and changes to the luni Ant scripts to help run it. The FileTest can be removed from the list of excluded test cases.
Best regards,
George
> 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
> Type: Bug
> Components: Classlib
> Environment: WinXP
> Reporter: George Harley
> Attachments: Harmony-248.txt
>
> 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
[jira] Updated: (HARMONY-248) Using java.io.File.deleteOnExit() and
System.runFinalizersOnExit(true) in the same application causes crash on
exit.
Posted by "George Harley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-248?page=all ]
George Harley updated HARMONY-248:
----------------------------------
Attachment: Support_DeleteOnExitWithRunFinalizersOnExitTest.java
New class for adding to the support/src/test/java/tests/support directory. Snappy name for a class isn't it ?
Best regards,
George
> 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
> Type: Bug
> Components: Classlib
> Environment: WinXP
> Reporter: George Harley
> Attachments: Harmony-248.txt, 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