Simple dynamic language using invokedynamic
John.Rose at Sun.COM
Mon Jun 22 19:42:27 PDT 2009
That reminds me of a bug we fixed in the mlvm patches during JavaOne;
it was a heap stomping problem. I don't think there was a workaround.
I think you have two options with this problem:
- wait for the mlvm changes to percolate into JDK7 and the JDK7
- obtain or build a version of the JVM from the mlvm patches (or have
you done this?)
On Jun 22, 2009, at 6:57 AM, Chanwit Kaewkasi wrote:
> I see, Remi !
> Thank you for the explanation.
> On Mon, Jun 22, 2009 at 2:43 PM, Rémi Forax<forax at univ-mlv.fr> wrote:
>> It's more a GC crash, with more memory you don't trigger the GC, that
>> why it's working fine.
More information about the mlvm-dev