Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JNI ERROR (app bug): weak global reference table overflow #463

Open
stefanstaniAIM opened this issue Sep 6, 2018 · 1 comment
Open

JNI ERROR (app bug): weak global reference table overflow #463

stefanstaniAIM opened this issue Sep 6, 2018 · 1 comment

Comments

@stefanstaniAIM
Copy link

stefanstaniAIM commented Sep 6, 2018

One of our customers reported that the app crashes sometimes.
He uses a ZebraMC33 ANDROID VERSION: 7.1.2

In log the following exception occurs in different versions. The exception JNI ERROR (app bug): weak global reference table overflow (max=51200)' is always the same, but the backtrace is different. I have attached different tombstone files. The exception doesn't occur at a certain dialog (layout) but at different ones.

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Zebra/MC33/MC33:7.1.2/01-01-49-NN-00-A/6:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 12388, tid: 12388, name: abris.developer  >>> com.eclipsesource.tabris.developer <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'art/runtime/indirect_reference_table.cc:132] JNI ERROR (app bug): weak global reference table overflow (max=51200)'
    x0   0000000000000000  x1   0000000000003064  x2   0000000000000006  x3   0000000000000008
    x4   0000000000000051  x5   0000000000000000  x6   0000000000000000  x7   feff666e6b61686b
    x8   0000000000000083  x9   ffffffffffffffdf  x10  0000000000000000  x11  0000000000000001
    x12  ffffffffffffffff  x13  ffffffffffffffff  x14  ff00000000000000  x15  ffffffffffffffff
    x16  0000007fb39deed0  x17  0000007fb3988934  x18  0000000000000000  x19  0000007fb4588b40
    x20  0000000000000006  x21  0000007fb4588a98  x22  000000000000000b  x23  0000007fb0586a68
    x24  000000000000000a  x25  ffffffffffffffff  x26  0000000000000cdb  x27  0000007fc33ec131
    x28  0000007fb05fc740  x29  0000007fc33ec030  x30  0000007fb3985dc4
    sp   0000007fc33ec010  pc   0000007fb398893c  pstate 0000000060000000
    v0   2e6761742e676f6c2e74736973726570  v1   0000007fc33ebb700000007fc33ebff0
    v2   000000000a0a0a2973746e656d656c65  v3   00000000000000000000000000000000
    v4   00000000401004000000000000000000  v5   40100401401004014010040140100401
    v6   00540000000000000054000000000000  v7   00000000000000000000000000000000
    v8   00000000000000000000000000000000  v9   00000000000000000000000000000000
    v10  00000000000000000000000000000000  v11  00000000000000000000000000000000
    v12  00000000000000000000000000000000  v13  00000000000000000000000000000000
    v14  00000000000000000000000000000000  v15  00000000000000000000000000000000
    v16  00000000000000000000000000000000  v17  00000000000000000000000041000000
    v18  0000000000000000000000003f800000  v19  00000000000000000000000000000000
    v20  00000000000000000000000000000000  v21  00000000000000000000000000000000
    v22  00000000000000000000000042640000  v23  00000000000000000000000042640000
    v24  00000000000000000000000000000000  v25  0000000000000000000000003f800000
    v26  00000000000000006f6f6f5f566f6f6f  v27  00000000000000006262627885626262
    v28  00000000000000006f6f6f838f6f6f6f  v29  0000000000000000a9a9a9b5bca9a9a9
    v30  0000000000000000ffffffffffffffff  v31  00000000000000000000000000000001
    fpsr 00000013  fpcr 00000000

backtrace:
    #00 pc 000000000006b93c  /system/lib64/libc.so (tgkill+8)
    #01 pc 0000000000068dc0  /system/lib64/libc.so (pthread_kill+64)
    #02 pc 0000000000024180  /system/lib64/libc.so (raise+24)
    #03 pc 000000000001cbec  /system/lib64/libc.so (abort+52)
    #04 pc 0000000000430f1c  /system/lib64/libart.so (_ZN3art7Runtime5AbortEPKc+456)
    #05 pc 00000000000e5898  /system/lib64/libart.so (_ZN3art10LogMessageD2Ev+1576)
    #06 pc 000000000024c3e8  /system/lib64/libart.so (_ZN3art22IndirectReferenceTable3AddEjPNS_6mirror6ObjectE+308)
    #07 pc 00000000002ef6f4  /system/lib64/libart.so (_ZN3art9JavaVMExt16AddWeakGlobalRefEPNS_6ThreadEPNS_6mirror6ObjectE+80)
    #08 pc 000000000034ebf8  /system/lib64/libart.so (_ZN3art3JNI16NewWeakGlobalRefEP7_JNIEnvP8_jobject+600)
    #09 pc 00000000000e25bc  /system/lib64/libandroid_runtime.so
    #10 pc 000000000235e0dc  /system/framework/arm64/boot-framework.oat (offset 0x1702000) (android.view.RenderNode.nCreate+152)
    #11 pc 000000000235dd08  /system/framework/arm64/boot-framework.oat (offset 0x1702000) (android.view.RenderNode.<init>+84)
    #12 pc 000000000235dee8  /system/framework/arm64/boot-framework.oat (offset 0x1702000) (android.view.RenderNode.create+84)
    #13 pc 00000000022be78c  /system/framework/arm64/boot-framework.oat (offset 0x1702000) (android.view.View.<init>+616)
    #14 pc 00000000022bea54  /system/framework/arm64/boot-framework.oat (offset 0x1702000) (android.view.View.<init>+112)
    #15 pc 000000000232df4c  /system/framework/arm64/boot-framework.oat (offset 0x1702000) (android.view.ViewGroup.<init>+88)
    #16 pc 000000000232dea4  /system/framework/arm64/boot-framework.oat (offset 0x1702000) (android.view.ViewGroup.<init>+64)
    #17 pc 000000000232de1c  /system/framework/arm64/boot-framework.oat (offset 0x1702000) (android.view.ViewGroup.<init>+56)
    #18 pc 000000000232dd98  /system/framework/arm64/boot-framework.oat (offset 0x1702000) (android.view.ViewGroup.<init>+52)
    #19 pc 00000000023456c0  /system/framework/arm64/boot-framework.oat (offset 0x1702000) (android.widget.FrameLayout.<init>+60)
    #20 pc 00000000005771d0  /data/app/com.eclipsesource.tabris.developer-2/oat/arm64/base.odex (offset 0x551000)

I'm already quite helpless how to fix it. So do you have any idea what the problem could be and how to fix it.

tombstone_04.txt
tombstone_05.txt
tombstone_07.txt
tombstone_08.txt
tombstone_09.txt
tombstone_00.txt
tombstone_01.txt
tombstone_02.txt
tombstone_03.txt

@mpost
Copy link
Member

mpost commented Sep 10, 2018

Is this issue tied to a concrete code piece called from the tabris side? Could it be that the Android implementation on that particular device has a problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants