Does anybody NOT use largeheap=true?

Solar2D Android
#1

I understand why Google doesn’t make this the default - I guess in theory that could allow more memory leaks to initially go unnoticed - but as a developer, if I’m confident that I’m properly managing memory, is there any downside to using largeheap=true?  I’m using it for all apps now and was just curious.

#2

I don’t use it at all, FWIW. I mostly work with pixelart, and all my memory leaks are self-inflicted so I haven’t had a need.

#3

There are probably many examples of apps that don’t use huge amounts of memory and don’t need a large heap to work well.  In fact a side effect of requesting a larger pool of memory to use is that other apps may get shut down instead of just being backgrounded.  I would say based on what I’ve read, you should only do this if you need extra memory above what is normally needed to run.

Rob

#4

Thanks Alex and Rob.  I think I wind up needing it because I use relatively large sprite sheets / high-res backgrounds, but the caveat of it shutting down other apps is good to know.

#5

I don’t use it at all, FWIW. I mostly work with pixelart, and all my memory leaks are self-inflicted so I haven’t had a need.

#6

There are probably many examples of apps that don’t use huge amounts of memory and don’t need a large heap to work well.  In fact a side effect of requesting a larger pool of memory to use is that other apps may get shut down instead of just being backgrounded.  I would say based on what I’ve read, you should only do this if you need extra memory above what is normally needed to run.

Rob

#7

Thanks Alex and Rob.  I think I wind up needing it because I use relatively large sprite sheets / high-res backgrounds, but the caveat of it shutting down other apps is good to know.