Unconventional and dodgy Android crash in during JNI/OpenGL ES loading code?

Posting from my earlier comments. "A JNI exception could be happening, and since you don't return after the exception, it could cause a crash. I don't know how Android's logging works, but in C a simple printf, need not output the log immediately.

So in the scenario when the crash occurred, it could be that an exception happened but the system crashed before the log could be output" Wasnt online for a few days. Hope the crash isnt back..I hate it when some issues magically disappear without a clear explanation. They usually come right back and bite you ;-) Anyway hope you don't get bitten.

I cant give a reply :(, I just had a similar issue and noticed that the java doc somewhere says when there is threading (if you are doing OpenGL then there is threading). You need to be carefull about the first parameter (env) and second parameter (jobject). You cant share the too on different threads because they are thread specific.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.