Native crash in unknown unknown

Question

I have an app which is entirely written in Java - no native code whatsoever - and I\'ve twice had a crash report on the Developer Console \"Native crash in unknown unknown\"

Answer 1

Searching has only revealed this type of crash in the case of Android bugs, NDK usage or buggy third party libraries

The fourth scenario is buggy ROMs, whether those ROMs are stock ROMs from a manufacturer or are ROM mods (e.g., CyanogenMod). Once-in-a-blue-moon sorts of crashes like this are most likely to come from ROM issues, as otherwise you would run into them more often.

Any suggestions for my next steps?

For only a couple of users, I wouldn't necessarily worry.

Otherwise, the Build fingerprint will give you some idea of the environment you are working with. In this case, samsung/m0xx would appear to be the Samsung GT-I9300, one of their "Galaxy S3" variants. If you can get your hands on one of those -- whether via outright purchase, some online testing service, or borrowing from a friend -- you could see if you can reproduce the crash and narrow down where in your code the crash is coming from. If you can do that, perhaps you can come up with some workaround that either is fine for all devices, or at least gets you past the crash on this one.

Answer 2

The bug report tells a few thing

• Build fingerprint: 'samsung/m0xx/m0:4.3/JSS15J/I9300XXUGMJ9:user/release-keys' It's an official Samsung ROM.
• signal 6 (SIGABRT) There was probably an internal error in a native library.
• #00 pc 0001c574 /system/lib/libc.so (epoll_wait+12) while waiting for a IO poll on an epoll file.
• #03 pc 0006bd21 /system/lib/libandroid_runtime.so (android::NativeMessageQueue::pollOnce(_JNIEnv*, int)+22) originally from the Android message queue.

Bottom line: it's very hard to tell what's happening.