but yeah thats what its looking like

the code generated appears to have some kind of nasty complexity between the number of recievers deep it is

if you look at the second chunk of the generated code its a wall of

$LOCALVARIABLE

asm stuff, far more than I would think necessary to run the relatively small block of source code its generating for

but that could be a misnomer, I've never written a line of jbc by hand and Im certainly no expert

it reads to me like somebody's written an O(n^2) memory complexity component in code with reciever lambda's

kotl.in/issue is where team works, so we ask to put requests there.

I really don't want to wrangle this down to an SSCCE because im pretty sure thats going to involve a lot of aggressive tuning of the JVM and its memory

run it with a max heap of 1MB

kind''ve thing

Can I ask somebody at JB to take a cursory look at this for me? Its a real pain in the ass and my only current solution is to drop the relevant file from the build process.