title: JNI called with jstring parameters, but one of them becomes NULL
body: <p>I'm calling native function from Java:</p>
  
  <pre><code>String pathTemp = Environment.getExternalStorageDirectory().getAbsolutePath()+Const.PATH_TEMP
  String pathFiles = Environment.getExternalStorageDirectory().getAbsolutePath()+Const.PATH_FILES
  engine.init(someInt, pathTemp, pathFiles);
  </code></pre>
  
  <p>And I have the native function:</p>
  
  <pre><code>extern "C" JNIEXPORT void Java_com_engine_init(JNIEnv *env, jobject __unused obj, jint someInt, jstring pathTemp, jstring pathFiles) {
  const char *pathTemp_ = env-&gt;GetStringUTFChars(pathTemp, JNI_FALSE); 
  const char *pathFiles_ = env-&gt;GetStringUTFChars(pathFiles, JNI_FALSE); // &lt;-- CRASH
  
  // More init code
  
  env-&gt;ReleaseStringUTFChars(pathTemp, pathTemp_);
  env-&gt;ReleaseStringUTFChars(pathRecording, pathRecording_);
  </code></pre>
  
  <p>}</p>
  
  <p>The problem: pathTemp is arriving good, but pathFiles==NULL in native function.
  Rechecked, and confirmed - both strings are non NULL in java.</p>
  
  <p>One more strange thing - The problem is on LG-G3 (android 6.0).
  On Meizu PRO 5 (android 7.0) - everything works good - both strings are intact.</p>
  
  <p>What is this JNI magic? Any clue?</p>