I am having trouble with memory leaks. I have one app with millions of installs. There are thousands of out of memory errors daily tracked on Google Analytics. Many of these, I was able to reduce. However, there are still significant problems.
In investigating the issue, there is a loss of 2 to 3K of free memory when orientation changes or a new activity is loaded and then closed.
I have attached a simple example. Switching orientation over and over eventually leads to a forced close with an out of memory error.
The attached example needs the VBBitmap library.
Is this an Android problem or something that could be improved in the generated java code?
Best regards,
Jack
In investigating the issue, there is a loss of 2 to 3K of free memory when orientation changes or a new activity is loaded and then closed.
I have attached a simple example. Switching orientation over and over eventually leads to a forced close with an out of memory error.
The attached example needs the VBBitmap library.
Is this an Android problem or something that could be improved in the generated java code?
Best regards,
Jack