RFC 7038914: VM could throw uncaught OOME in ReferenceHandler thread (original) (raw)
Thomas Schatzl thomas.schatzl at oracle.com
Thu May 16 10:44:46 UTC 2013
- Previous message: RFC 7038914: VM could throw uncaught OOME in ReferenceHandler thread
- Next message: RFC 7038914: VM could throw uncaught OOME in ReferenceHandler thread
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi all,
On Mon, 2013-05-13 at 13:55 +0200, Thomas Schatzl wrote:
Hi all,
I updated the test program and the patch in java.lang.ref.Reference accordingly. As for the problem of reproducibility, in my tests I had a 100% reproduction rate with the previous version of the test. However, now I also set -XX:-UseTLAB and -Xmx16M in the test program as suggested in some other emails. I will report back with a new webrev after some testing on more platforms as suggested by David.
a new webrev for the patch is at
http://cr.openjdk.java.net/~tschatzl/7038914/webrev.2/
Testing: jprt; manual tests with the test program on a jdk with and without the patch on linux 32/64 bit, windows 32/64 bit, and sparc 32/64 bit. The test program showed 100% reproduction of the error without the patch, and 100% fix success with a jdk containing the patch (each multiple tries at that). Note that jprt seems to run all jdk unit tests always anyway.
I also fixed the copyright date in java/lang/ref/Reference.java.
If this patch is considered acceptable, I need two reviewers as usual (possibly from GC/hsx team and one from jdk), and one sponsor pushing the change. (I am still intent on making Peter the author of the patch as both the change and the test program came from him)
I am not even author for the jdk, but can act as a non-Reviewer reviewer for the gc/hsx team.
Thanks a lot, Thomas
- Previous message: RFC 7038914: VM could throw uncaught OOME in ReferenceHandler thread
- Next message: RFC 7038914: VM could throw uncaught OOME in ReferenceHandler thread
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]