AOT Engine Error: Class too large about chicory HOT 10 OPEN

Thanks for reporting!

Might be related: #405

There is work being done to split methods that are too large. In the meantime could you try: -XX:-DontCompileHugeMethods

That seemed to work for me when the compiled method was on the edge of being too big.

from chicory.

You could also try some running wasm-opt and other post processing optimizers on the resulting module. Some things may not be runnable until we can split methods though.

from chicory.

I think it's in the same category as #405. I interpreted the error as ASM saying, "I can't generate your class bytecode because it is invalid." It seems to me that this step would come before the decision to natively compile the methods (e.g. rendering the DontCompileHugeMethods JVM arg irrelevant), is that correct or am I misunderstanding?

I've tried wasm-opt, but the output wasms from various optimization levels are always unstable / crashy.

from chicory.

Yes, definitely a different error and earlier in the process. I'm unsure if the method splitting work would address this const pool issue. @electrum is working on this and he would know.

from chicory.

The -XX:-DontCompileHugeMethods flag is to allow the JVM JIT to work for large methods. The error here is that the WASM method is to large to convert to a single JVM method. So these aren't really related (other than that method splitting might prevent the need for that JVM flag).

from chicory.

If you could provide a reproduction, possibly based on #450, that would be helpful to ensure that the method splitting will work for this. What does your original method look like?

from chicory.

The constant pool issue might require splitting the methods across multiple classes, as you suggest. It's hard to say what might be required without seeing an example of the WASM input. I'm not sure if there is a good generic solution to this problem, as it is easy to construct pathological cases given the much larger WASM limits compared to JVM bytecode.

from chicory.

I can't supply the specific WASM, but I'll try to take a closer look at the class file that is attempting to be generated and try to get a grasp of what is going on there.

from chicory.

Seeing what is in the constant pool would be helpful.

from chicory.

@heroicefforts Could you send us a dump of the constant pool? You could obfuscate it if necessary.

from chicory.