Menu ▾ ▴

#630 ProGuard 5.3.1 crashes with NPE at NonEmptyStackReturnMarker.setReturnsWithNonEmptyStack

v5.3
closed-fixed
None
5
2017-04-01
2016-11-29
Amal
No

Stuck on exception in the ProGuard 5.3.1. Can't build android application.
ProGuard 5.2.1 worked fine with this app.

Versions:
Gradle 3.2.1
com.android.tools.build:gradle:2.2.2
net.sf.proguard:proguard-base:5.3.1

All optimizations enabled except:
-optimizations !class/merging/horizontal

Other settings:
-optimizationpasses 1
-allowaccessmodification
-dontobfuscate
-target 1.6
-verbose
-dontpreverify
-dontskipnonpubliclibraryclasses
-dontskipnonpubliclibraryclassmembers

java.io.IOException: java.lang.NullPointerException
    at com.android.build.gradle.internal.transforms.ProGuardTransform.doMinification(ProGuardTransform.java:268)
    at com.android.build.gradle.internal.transforms.ProGuardTransform.access$000(ProGuardTransform.java:61)
    at com.android.build.gradle.internal.transforms.ProGuardTransform$1.run(ProGuardTransform.java:170)
    at com.android.builder.tasks.Job.runTask(Job.java:51)
    at com.android.build.gradle.tasks.SimpleWorkQueue$EmptyThreadContext.runTask(SimpleWorkQueue.java:41)
    at com.android.builder.tasks.WorkQueue.run(WorkQueue.java:223)

Caused by: java.lang.NullPointerException
    at proguard.optimize.info.NonEmptyStackReturnMarker.setReturnsWithNonEmptyStack(NonEmptyStackReturnMarker.java:102)
    at proguard.optimize.info.NonEmptyStackReturnMarker.markReturnWithNonEmptyStack(NonEmptyStackReturnMarker.java:95)
    at proguard.optimize.info.NonEmptyStackReturnMarker.visitSimpleInstruction(NonEmptyStackReturnMarker.java:76)
    at proguard.classfile.instruction.visitor.MultiInstructionVisitor.visitSimpleInstruction(MultiInstructionVisitor.java:88)
    at proguard.classfile.instruction.SimpleInstruction.accept(SimpleInstruction.java:218)
    at proguard.classfile.attribute.CodeAttribute.instructionsAccept(CodeAttribute.java:138)
    at proguard.classfile.attribute.CodeAttribute.instructionsAccept(CodeAttribute.java:110)
    at proguard.classfile.instruction.visitor.AllInstructionVisitor.visitCodeAttribute(AllInstructionVisitor.java:54)
    at proguard.classfile.attribute.visitor.MultiAttributeVisitor.visitCodeAttribute(MultiAttributeVisitor.java:245)
    at proguard.classfile.attribute.CodeAttribute.accept(CodeAttribute.java:101)
    at proguard.classfile.ProgramMethod.attributesAccept(ProgramMethod.java:81)
    at proguard.classfile.attribute.visitor.AllAttributeVisitor.visitProgramMember(AllAttributeVisitor.java:95)
    at proguard.classfile.util.SimplifiedVisitor.visitProgramMethod(SimplifiedVisitor.java:92)
    at proguard.classfile.visitor.MultiMemberVisitor.visitProgramMethod(MultiMemberVisitor.java:92)
    at proguard.classfile.ProgramMethod.accept(ProgramMethod.java:73)
    at proguard.classfile.ProgramClass.methodsAccept(ProgramClass.java:516)
    at proguard.classfile.visitor.AllMethodVisitor.visitProgramClass(AllMethodVisitor.java:47)
    at proguard.classfile.visitor.MultiClassVisitor.visitProgramClass(MultiClassVisitor.java:85)
    at proguard.classfile.ProgramClass.accept(ProgramClass.java:358)
    at proguard.classfile.ClassPool.classesAccept(ClassPool.java:124)
    at proguard.optimize.Optimizer.execute(Optimizer.java:649)
    at proguard.ProGuard.optimize(ProGuard.java:328)
    at proguard.ProGuard.execute(ProGuard.java:127)
    at com.android.build.gradle.internal.transforms.BaseProguardAction.runProguard(BaseProguardAction.java:54)
    at com.android.build.gradle.internal.transforms.ProGuardTransform.doMinification(ProGuardTransform.java:239)
    ... 5 more

Discussion

  • Amal

    Amal - 2016-11-29

    It seems like the problem only appears when I include big "nosideffects" file. Attached it.

     
  • Eric Lafortune

    Eric Lafortune - 2016-12-18

    Thanks for your report. This issue has now been fixed for the upcoming ProGuard version 5.3.3 (essentially with a null check at the reported location).

     

    Last edit: Eric Lafortune 2016-12-18
  • Eric Lafortune

    Eric Lafortune - 2016-12-18
    • status: open --> open-fixed
    • assigned_to: Eric Lafortune
     
  • Kirill Rakhman

    Kirill Rakhman - 2016-12-20

    When is 5.3.3 expected to be released?

     
  • Scott Pierce

    Scott Pierce - 2017-03-03

    When is 5.3.3 being released? We're encountering this bug also.

     
  • Scott Kennedy

    Scott Kennedy - 2017-03-29

    Any update? The bug has been "fixed" for months, but without a new release, this is causing major headaches building Android apps.

     
  • Eric Lafortune

    Eric Lafortune - 2017-04-01

    This actually a duplicate of bug #623, which contains a patch if necessary. A status "open-fixed" indeed means that the fix is not available in a public release yet.

     
  • Eric Lafortune

    Eric Lafortune - 2017-04-03
    • Status: open-fixed --> closed-fixed
     

Log in to post a comment.