| Issue 156: | IS there solution for the jni ReferenceTable overflow problem ? | |
| 3 people starred this issue and may be notified of changes. | Back to list |
11284-11284/am.locator.places W/dalvikvm: ReferenceTable overflow (max=1024) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: JNI pinned array reference table (0x5bf3a0) dump: 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: Last 10 entries (of 1024): 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 1023: 0x420200d0 char[] (26 elements) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 1022: 0x4201fa90 char[] (41 elements) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 1021: 0x4201f5c8 char[] (16 elements) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 1020: 0x4201f1f0 char[] (26 elements) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 1019: 0x4201ece0 char[] (26 elements) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 1018: 0x4201e760 char[] (16 elements) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 1017: 0x4201e158 char[] (41 elements) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 1016: 0x4201dd00 char[] (26 elements) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 1015: 0x4201d7f0 char[] (26 elements) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 1014: 0x4201d260 char[] (26 elements) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: Summary: 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 416 of char[] (16 elements) (416 unique instances) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 507 of char[] (26 elements) (507 unique instances) 07-22 13:32:50.195 11284-11284/am.locator.places W/dalvikvm: 101 of char[] (41 elements) (101 unique instances) 07-22 13:32:50.195 11284-11284/am.locator.places E/dalvikvm: Failed adding to JNI pinned array ref table (1024 entries) 07-22 13:32:50.200 11284-11284/am.locator.places A/libc: Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1) I'm using Android 4.0.3
Apr 14, 2014
#1
rafael.c...@gmail.com
Apr 15, 2014
Humm actually we had a problem with a JNI call we did. Mainly because we were using GetByteArrayRegion without a ReleaseByteArray. This link helps a lot: http://developer.android.com/training/articles/perf-jni.html#arrays |