Eric House 9cdd5a7b72 share mpool and vtable in jni calls ... A number of jni calls were "stateless", which meant they allocated their own vtmgr and mpool instances each time invoked. Instead invoke them with the global jni closure and add to it vtmgr (already has mpool) and use these instead of allocating/freeing each time. To make sure no race conditions are introduced (mpool, though debug-only, is probably not thread-safe), guard these new uses with an in-use flag. If that fires I'll need a mutex or something.		2018-06-27 21:17:44 -07:00
..
src	share mpool and vtable in jni calls	2018-06-27 21:17:44 -07:00
build.gradle	upgrade AS and gradle and with luck travis will work	2018-05-06 14:33:10 -07:00
debug.keystore	include debug keystore directly	2017-01-22 15:35:02 -08:00
proguard-rules.pro	tweak comments	2017-07-19 06:16:22 -07:00