Performance - Out Of Memory

[fee1-dead]

I have seen many issues reporting the same issue. So I will open this and merge all the duplicates here.

There are two kinds of messages: Java heap space and GC overhead limit exceeded.

This could be resolved by increasing the heap space with -Xmx such as -Xmx6G, but in other cases, the jar attempted for deobfuscation could be very large and it could not be resolved.

Here are some possible solutions if that is the case.

• Transform the classes with only one transformer every time
• Split the jar file into many jars, only deobfuscating a part of the program while having other parts as libraries.
• Avoid loading redundant classpath jars.
• Use other tools (e.g. ProGuard)

Could also be related to JavaVM.

[Janmm14]

Lazy loading of classes out of the path jars might help here.

[fee1-dead]

Or, instead of loading classes as class nodes, only use a class which implements ClassVisitor, which only receives the superclass and interface info.

[Janmm14]

Or use the current style of asm api but with SKIP_CODE flag. Visitor API is kind neat as its faster, but we're using the OOP API everywhere here.

[x4e]

User error, buy more ram

[Maskhe]

then....how to solve this problem?I am not very clear about the solutions mentioned above 😢

[I2rys]

Hello @Maskhe,
Use allatori.string.StringEncryptionTransformer as your transformer or increase your java heap space using -Xmx or -Xmx6G and It will be fixed, It worked for me.