Detected by the user @Marcior on 16 June 2013
http://forums.coronalabs.com/topic/27207-resolved-problems-savingloading-photos-from-album-on-android/page-2
“Okay, so, we were able to reproduce this issue. We are definitely detecting a slight memory leak everytime you suspend/resume an app and after doing this enough times, the app exceeds the max heap limit on Android. We think we’ve isolated this issue in our core C++ code, which unfortunately means we can only fix this in a daily build. Also, theoretically, this issue should only happen on Android and Windows. Mac and iOS may not have this issue. This also looks like a graphics 2.0 issue as well. We’ll investigate this further and let you know once we have it resolved. Thanks for bringing up this issue.”
Joshua Quick 20 March 2014 - 01:53 AM
“We think we’ve narrowed it down to a bug in Google’s GLSurfaceView class in Java, because when we grabbed the newest version of that class from GitHub (Google open sources most of the Android OS), the memory leak went away. However, in doing so, it introduced some new issues that prevented us from making that change. Unfortunately, this issue still requires quite a bit of experimentation on our end to find a solution. We don’t have an ETA yet.”
Joshua Quick 23 April 2014
“We have a fix coming for the Photo Picker when opening large photos multiple times. The memory leak is caused by a bug in one of the Google libraries. We tried replacing the library with their updated version but it causes other bugs so we are sorting out the issues now.”
Tom 07 May 2014
"Engineering has had two days to try and sort out the problems they mentioned above. Please be patient. Not all bugs can be fixed at the speed of light, especially problems in libraries out of our control.
Thanks"
Rob Miracle 11 May 2014
Still Waiting… and please, don’t put the blame on Google or hide the post, there are thousand of photo apps, and only Corona’s one has that problem.