Name |
Date |
Size |
#Lines |
LOC |
||
---|---|---|---|---|---|---|
.. | - | - | ||||
jni/ | 03-May-2024 | - | 294 | 178 | ||
res/ | 03-May-2024 | - | 214 | 149 | ||
src/com/android/benchmark/moarram/ | 03-May-2024 | - | 71 | 54 | ||
Android.mk | D | 03-May-2024 | 941 | 32 | 8 | |
AndroidManifest.xml | D | 03-May-2024 | 784 | 24 | 20 | |
README.txt | D | 03-May-2024 | 884 | 18 | 14 |
README.txt
1This is a simple app that can be used as a tutorial or reference benchmark 2for the development of the DDMS native heap tracker feature. It contains 3 3unique paths to allocate heap chunks: 4 51) Java_com_android_benchmark_moarram_MainActivity_add32ByteBlocksNative in 6 foo.c (libmoarram-foo.so). Each invocation will allocate 32 bytes. 72) Java_com_android_benchmark_moarram_MainActivity_add2MByteBlocksNative in 8 bar.c (libmoarram-bar.so). Each invocation will allocate 2M bytes. 93) Java_com_android_benchmark_moarram_MainActivity_addVariableSizedBlocksNative 10 in baz.c (libmoarram-baz.so). Each invocation will allocate 17 or 71 bytes, 11 depending on the active button in a radio group. 12 13Each allocation can be freed by clicking the corresponding free button in the 14UI. 15 16NOTE 09/16/2013 17A new feature is added to force a double free. Both debug libc and Valgrind can capture it. 18