diff options
| author | 2010-08-18 15:40:29 +0800 | |
|---|---|---|
| committer | 2010-08-19 12:21:44 +0800 | |
| commit | 291303ba3dbb3a0173bcc82ded595ca75df7b50e (patch) | |
| tree | 8df16ec637091c70ce3622e2cfeeaf15f8793afc /libs/utils/ZipFileRO.cpp | |
| parent | 6ab94608750776bcaaee56696cfcfb16ce29db8a (diff) | |
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
Diffstat (limited to 'libs/utils/ZipFileRO.cpp')
0 files changed, 0 insertions, 0 deletions