Wei-Ta Chen 291303ba3d Fix a bug, where one thread is using JNIEnv associated with another thread.
We see abort messages like this when using JavaPixelAllocator and JavaMemoryUsageReporter.
W/dalvikvm(  680): JNI WARNING: threadid=2 using env from threadid=10
W/dalvikvm(  680):              in Landroid/graphics/LargeBitmap;.nativeClean (I)V (CallVoidMethodV)

To fix it, we keep JavaVM, rather than JNIEnv, in JavaPixelAllocator and JavaMemoryUsageReporter,
because JavaVM allows us to get the JNIEnv corresponds to the current thread.

Change-Id: Ibd4b394a53dd3fdccc5a442eeb0dedf836479575
2010-08-19 12:21:44 +08:00
2010-08-04 13:15:12 -07:00
2010-08-17 14:34:02 +08:00
2010-08-17 19:40:26 -07:00
2010-08-17 19:40:26 -07:00
2010-08-11 00:29:59 -07:00
2010-03-16 09:59:06 -07:00
2010-08-18 10:21:10 +08:00
2010-08-16 18:02:31 +08:00
2010-03-29 18:12:24 -07:00
2010-08-17 16:45:53 -07:00
Description
No description provided
21 GiB
Languages
Java 73.7%
Kotlin 14%
PowerBuilder 5.8%
C++ 5.2%
AIDL 1%