#456 VerifyError in Android from code/allocation optimization

v4.8
open
7
2014-10-01
2012-09-26
Sean Owen
No

Eric I don't know if this is enough to go on or start with, but:

I get this VerifyError from dalvikvm when running an app optimized with Proguard 4.8:

W/dalvikvm(27825): VFY: Ljava/lang/Object; is not instance of Ljava/lang/String;
W/dalvikvm(27825): VFY: bad arg 1 (into Ljava/lang/String;)
W/dalvikvm(27825): VFY: rejecting call to Ljava/lang/StringBuilder;.append (Ljava/lang/String;)Ljava/lang/StringBuilder;
W/dalvikvm(27825): VFY: rejecting opcode 0x6e at 0x0056
W/dalvikvm(27825): VFY: rejected Lcom/srowen/bs/android/history/e;.a (Ljava/lang/String;Ljava/lang/String;)V
W/dalvikvm(27825): Verifier rejected class Lcom/srowen/bs/android/history/e;
D/AndroidRuntime(27825): Shutting down VM
W/dalvikvm(27825): threadid=1: thread exiting with uncaught exception (group=0x41d56300)
E/AndroidRuntime(27825): FATAL EXCEPTION: main
E/AndroidRuntime(27825): java.lang.VerifyError: com/srowen/bs/android/history/e

I know that disabling code/allocation/* makes it go away.

The source code in question is, presumably, buildHistory() here:

http://code.google.com/p/zxing/source/browse/trunk/android/src/com/google/zxing/client/android/history/HistoryManager.java

I figured there's a chance this would pinpoint an issue.

Discussion

  • Eric Lafortune

    Eric Lafortune - 2012-09-26

    I've fixed a similar-sounding issue somewhere. Could you check if ProGuard 4.9 beta1 perhaps fixes the problem?

     
  • Eric Lafortune

    Eric Lafortune - 2012-09-26
    • assigned_to: nobody --> lafortune
    • priority: 5 --> 7
     
  • Sean Owen

    Sean Owen - 2012-09-26

    I tried; it gets into some kind of loop that makes it run out of memory eventually on my code. You want that stack trace? :)

     
  • Eric Lafortune

    Eric Lafortune - 2012-09-26

    Ouch! I'll try both versions myself first.

     
  • HRDudhat

    HRDudhat - 2014-10-01

    @Eric I am using proguurd v4.7 which is provided in android SDK.

    In my app I have integrated Zxing libraty and I am getting same error while configuring proguard.

    I have attached updated proguard-android-optimize.txt which currently used in my ZXing lib.

    Can you please help me to resolve the issue? Because my app is on deploy stage.

     
    Last edit: HRDudhat 2014-10-01

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks