Hi,
we are developing an OpenGl Android game in Java.
Currently we are facing OutOfMemoryErrors, while we are loading the data
and allocating direct ByteBuffers.
We have read alot on contradictory statements about the limitations of the
native heap,if there's a hard limit or not for the native heap and/or the
overallprocess heap.
Maybe some of you can help out with some clarification on these specifics.
Is there a difference concerning the memory limits for JNI native memory
usage in a Java-App and a pure NDK app?
Are there possibilities to circumvent these limitations, that are
performing faster than e.g. mmapped files? It is very
hard, if not impossible to handle all our data within a 24MB limit, e.g.
textures aren't present for most of our objects yet.
Some more details:
As for textures and geometry data we use direct buffers, they contain
the most data of the application. So our memory footprint roughly looks
like this:
5mb vm-heap used
5mb vm-heap fre
17mb native heap used
Thanks in advance,
Flo
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
