#169 StackOverflowError while optimizing

[Gili Tzabari]

Hi,

I get the following stack-trace while optimizing. I
hope this is enough for you to track down the problem.

java.lang.StackOverflowError
at
proguard.optimize.evaluation.value.SpecificReferenceValue.generalize(SpecificReferenceValue.java:62)
at
proguard.optimize.evaluation.value.ReferenceValue.generalize(ReferenceValue.java:161)
at
proguard.optimize.evaluation.Variables.generalize(Variables.java:133)
at
proguard.optimize.evaluation.TracedVariables.generalize(TracedVariables.java:142)
at
proguard.optimize.evaluation.PartialEvaluator.evaluateInstructionBlock(PartialEvaluator.java:575)
[...snip...]
at
proguard.optimize.evaluation.PartialEvaluator.evaluateInstructionBlock(PartialEvaluator.java:785)
at
proguard.optimize.evaluation.PartialEvaluator.evaluate(PartialEvaluator.java:103)
at
proguard.optimize.evaluation.EvaluationSimplifier.visitCodeAttrInfo(EvaluationSimplifier.java:178)
at
proguard.classfile.attribute.CodeAttrInfo.accept(CodeAttrInfo.java:134)
at
proguard.classfile.ProgramMethodInfo.attributesAccept(ProgramMethodInfo.java:76)
at
proguard.optimize.evaluation.EvaluationSimplifier.visitProgramMethodInfo(EvaluationSimplifier.java:114)
at
proguard.classfile.ProgramMethodInfo.accept(ProgramMethodInfo.java:68)
at
proguard.classfile.ProgramClassFile.methodsAccept(ProgramClassFile.java:507)
at
proguard.classfile.visitor.AllMethodVisitor.visitProgramClassFile(AllMethodVisitor.java:47)
at
proguard.classfile.ProgramClassFile.accept(ProgramClassFile.java:400)
at
proguard.classfile.ClassPool.classFilesAccept(ClassPool.java:126)
at proguard.optimize.Optimizer.execute(Optimizer.java:208)
at proguard.ProGuard.optimize(ProGuard.java:278)
at proguard.ProGuard.execute(ProGuard.java:99)
at
proguard.gui.ProGuardRunnable.run(ProGuardRunnable.java:85)
at java.lang.Thread.run(Unknown Source)

[Gili Tzabari]

Logged In: YES
user_id=80628

Sorry, duplicate of #1470139. Isn't there a way to shrink
Proguard's stack usage?

[Eric Lafortune]

Logged In: YES
user_id=555208

You can work around the problem by switching off
optimization (or by working in Linux).