Bug 1603499 Comment 6 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I can kind of help with this:

If native code calls into java through JNI, and an exception was thrown in the java code, we get a crash in `Accessor::EndAccess`, which is indicative that an exception was thrown. The `.extra` file contains additional data about the java exception via the [`JavaStackTrace` annotation](https://searchfox.org/mozilla-central/rev/cfd1cc461f1efe0d66c2fdc17c024a203d5a2fd8/widget/android/jni/Utils.cpp#223).

I'm not sure if snorp has any other comments, so I'll leave his needinfo.
Revision 1 by
on 
I can kind of help with this:

If native code calls into java through JNI, and an exception was thrown in the java code, we get a crash in `Accessor::EndAccess` once the thread returns back to native, indicating that a java exception was thrown. The `.extra` file contains additional data about the java exception via the [`JavaStackTrace` annotation](https://searchfox.org/mozilla-central/rev/cfd1cc461f1efe0d66c2fdc17c024a203d5a2fd8/widget/android/jni/Utils.cpp#223).

I'm not sure if snorp has any other comments, so I'll leave his needinfo.
Revision 2 by
on 
I can kind of help with this:

If native code calls into java through JNI, and an exception was thrown in the java code, we get a crash in `Accessor::EndAccess` once the thread returns back to native. The `.extra` file contains additional data about the java exception via the [`JavaStackTrace` annotation](https://searchfox.org/mozilla-central/rev/cfd1cc461f1efe0d66c2fdc17c024a203d5a2fd8/widget/android/jni/Utils.cpp#223).

I'm not sure if snorp has any other comments, so I'll leave his needinfo.

Back to Bug 1603499 Comment 6