Re: JVMTI OOM handling when arrays / objects are too large

2009-06-16 Thread Jeremy Manson
Not that I actually have a vote, but if Alan feels it is not worth making, I would go back to arguing for something like a VirtualMachineError to be thrown, because the behavior is out of spec. The current behavior - a sort-of-but-not-really OOME - is a little odd. Jeremy On Tue, Jun 16, 2009 at

Re: JVMTI OOM handling when arrays / objects are too large

2009-06-16 Thread Martin Buchholz
The resolution of this is still uncertain. We have one approval I think, but all of the maintainers have expressed reluctance at making this change. I continue to agree with Jeremy and be in favor of making this change, but it's no big deal either way. Perhaps Alan's opinion is authoritative, since

hg: jdk7/tl/jdk: 6850783: InvalidityDateExtension returns reference to internal mutable state

2009-06-16 Thread xuelei . fan
Changeset: 1299804aa6e7 Author:xuelei Date: 2009-06-16 20:46 +0800 URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/1299804aa6e7 6850783: InvalidityDateExtension returns reference to internal mutable state Summary: return cloned instead of referenced object Reviewed-by: weijun ! src

hg: jdk7/tl/langtools: 4 new changesets

2009-06-16 Thread maurizio . cimadamore
Changeset: a9c04a57a39f Author:mcimadamore Date: 2009-06-16 10:45 +0100 URL: http://hg.openjdk.java.net/jdk7/tl/langtools/rev/a9c04a57a39f 6845686: basic and raw formatters do not display captured var id properly when javac runs in -XDoldDiags mode Summary: Basic and raw formatters