Back to all discussions

  •   over 10 years ago

unhandled JNI exception

Hello,

I sometimes receive the following exception that I cannot handle since it comes from JNI. (using the Intersector.intersectWithTarget method)

I/DEBUG (17256): #00 pc 00024c60 /data/app-lib/com.michaal.collaborativemind-23/libInkingEngine.so
I/DEBUG (17256): #01 pc 00025649 /data/app-lib/com.michaal.collaborativemind-23/libInkingEngine.so
I/DEBUG (17256): #02 pc 0001e98c /system/lib/libdvm.so (dvmPlatformInvoke+112)
I/DEBUG (17256): #03 pc 0004f313 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
I/DEBUG (17256): #04 pc 00027da0 /system/lib/libdvm.so
I/DEBUG (17256): #05 pc 0002eddc /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
I/DEBUG (17256): #06 pc 0002c440 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
I/DEBUG (17256): #07 pc 00061739 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+336)
I/DEBUG (17256): #08 pc 0006175d /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
I/DEBUG (17256): #09 pc 0005644b /system/lib/libdvm.so
I/DEBUG (17256): #10 pc 0000d280 /system/lib/libc.so (__thread_entry+72)
I/DEBUG (17256): #11 pc 0000d418 /system/lib/libc.so (pthread_create+240)

  • 3 comments

  • Manager   •   over 10 years ago

    Hello!

    Thanks for your question. We're checking with the Wacom team and will be back with their response shortly.

    Best,
    Serena

  •   •   over 10 years ago

    Hello,

    A full stacktrace would be helpful.

    However, this exception can be caused by several different reasons:
    - The target of the intersection is invalid: invalid native points buffer (deallocated or modified after setting the target), size, stride and/or width.
    - An invalid intersectable instance passed to the intersectWithTarget(E...) method: invalid native points buffer, size, stride, bounds and/or width.

    Regards,

    Zahari,
    Wacom WILL team

  •   •   over 10 years ago

    Hello Zahari,

    Thank you. It turned out I was writing to the same floatbuffer while I was encoding it in another thread, so the receiving end was getting the encoded message all messed up.

    Best regards.

Comments are closed.