[Jython-users] Compilation unit size exploding in JVM

[Jeff M. <jef...@za...>]

Was just reminded about an issue I had back in December; I don't have
logfile evidence handy but may be able to generate some if needed.

There seems to be an emitted unit sizing issue in 2.7 -- ie: python code
that ran just fine in 2.5 sometimes blows up in 2.7 when the JVM tries to
invoke it; the on the fly compilation may be dumping in too many tokens or
something.

The workaround I had at the time was to try a few earlier builds of 2.7 or
just go back to 2.5 .. ie: the standard 2.7 from the website, vs the most
recent from the source repo. IIRC, the more recent the release, the larger
the space used, and the higher chance the JVM would reject it. 2.5 had no
problems whatsoever.

JVM being openjdk in this case on a linux VM.

Without the logfiles on hand its hard to pull out the correct keywords
here,but does this ring a bell with anyone?

I seem to recall there was no easy JVM tweak to work around it short of
recompiling the JVM (ugh), but I expected the issue may just take care of
itself later, and it wasn't critical for me at the time.

Anyone know if this is a known issue? resolved? or an ongoing concern?

jeff