Lines Matching refs:Release

200 between threads, and are valid until the matching Release call.)</p>
226 <p><strong>Don't forget to <code>Release</code> the strings you <code>Get</code></strong>.  The
229 are guaranteed valid until <code>Release</code> is called, which means they are not
252 is guaranteed to be valid until the corresponding <code>Release</code> call
255 <strong>You must <code>Release</code> every array you <code>Get</code>.</strong>  Also, if the <cod…
256 call fails, you must ensure that your code doesn't try to <code>Release</code> a NULL
263 <p>The <code>Release</code> call takes a <code>mode</code> argument that can
288 you need to call <code>Release</code> with <code>JNI_COMMIT</code>
299 <p>It is a common mistake (repeated in example code) to assume that you can skip the <code>Release<…
305 and you will need to call <code>Release</code> again with a different flag
326 The code copies the data (for perhaps a second time), then calls <code>Release</code>; in this case
337     to call <code>Release</code> after something fails.
367     <li><code>Release&lt;PrimitiveType&gt;ArrayElements</code>
418 <li>Release modes: passing a bad release mode to a release call (something other than <code>0</code…