java.lang.IllegalArgumentException: Stack size becomes negative after instruction [24] swap in [ElvisKt.main([Ljava/lang/String;)V]

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via proguard by max-kammerer
, 1 year ago
Stack size becomes negative after instruction [24] swap in [ElvisKt.main([Ljava/lang/String;)V]
via proguard by cowwoc
, 1 year ago
Stack size becomes negative after instruction \[192\] astore v5 in \[org/apache/derby/impl/services/daemon/BasicDaemon.run()V\]
via proguard by nagkumar
, 1 year ago
Stack size becomes negative aft er instruction \[106\] ificmpge +6 (target=112) in \[com/tejasoft/j2me/common/ui/nb /table/TableItem.paint(Ljavax/microedition/lcdui/Graphics;II)V\]
via proguard by horschi
, 1 year ago
Stack size becomes negative after instruction  swap in
via GitHub by burton999dev
, 7 months ago
Stack size becomes negative after instruction [149] invokestatic #42 in [com/birbit/android/jobqueue/Job.safeRun(Lcom/birbit/android/jobqueue/JobHolder;ILcom/birbit/android/jobqueue/timer/Timer;)I]
java.lang.IllegalArgumentException: Stack size becomes negative after instruction [24] swap in [ElvisKt.main([Ljava/lang/String;)V]
at proguard.classfile.attribute.visitor.StackSizeComputer.evaluateInstructionBlock(StackSizeComputer.java:334)
at proguard.classfile.attribute.visitor.StackSizeComputer.visitBranchInstruction(StackSizeComputer.java:197)
at proguard.classfile.instruction.BranchInstruction.accept(BranchInstruction.java:140)
at proguard.classfile.attribute.visitor.StackSizeComputer.evaluateInstructionBlock(StackSizeComputer.java:355)
at proguard.classfile.attribute.visitor.StackSizeComputer.visitCodeAttribute0(StackSizeComputer.java:153)
at proguard.classfile.attribute.visitor.StackSizeComputer.visitCodeAttribute(StackSizeComputer.java:110)
at proguard.optimize.peephole.MethodInliner.visitCodeAttribute0(MethodInliner.java:200)
at proguard.optimize.peephole.MethodInliner.visitCodeAttribute(MethodInliner.java:152)
at proguard.classfile.attribute.CodeAttribute.accept(CodeAttribute.java:101)
at proguard.classfile.ProgramMethod.attributesAccept(ProgramMethod.java:79)
at proguard.classfile.attribute.visitor.AllAttributeVisitor.visitProgramMember(AllAttributeVisitor.java:95)
at proguard.classfile.util.SimplifiedVisitor.visitProgramMethod(SimplifiedVisitor.java:92)
at proguard.classfile.ProgramMethod.accept(ProgramMethod.java:71)
at proguard.classfile.ProgramClass.methodsAccept(ProgramClass.java:516)
at proguard.classfile.visitor.AllMethodVisitor.visitProgramClass(AllMethodVisitor.java:47)
at proguard.classfile.ProgramClass.accept(ProgramClass.java:358)
at proguard.classfile.ClassPool.classesAccept(ClassPool.java:124)
at proguard.optimize.Optimizer.execute(Optimizer.java:750)
at proguard.ProGuard.optimize(ProGuard.java:328)
at proguard.ProGuard.execute(ProGuard.java:127)
at proguard.ProGuard.main(ProGuard.java:538)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.