I found a memory leak in the iOS Runtime introduced in 3.0. Thanks for any feedback you have in advance, I've tried a few my own, but there are a few internal classes in the runtime I can't inspect so my hands are a bit tied in this case. I hope this app will help in identifying and verifying possible solutions. Please tell us how to recreate the issue in as much detail as possible.įollow the instruction in the "Fully automated Out Of Memory Crash App". IOS (didn't check Android) Please provide the following version numbers that your issue occurs with: Which platform(s) does your issue occur on? The problem with both apps is exactly the same: memory is retained.
It has lots more graphics and styling than this demo, so I had to add a lot of labels and automated navigation to reach the same level of memory pressure my app has. The app crashes after about 20 minutes of usage on an iPad Air (1GB RAM).
While this may seem very artificial, I actually created this app to demonstrate a problem I saw in a real app. As you can see it's growing with every visit of the listview. Note this is a screenshot of the app after going back and forth exactly 172 times (as shown in the app's screenshot), and the blue graph on the right is Xcode reporting the heap size over time. Back-navigation doesn't clear the memory of the listview (inspecting the heap it mostly looks like retained labels, but I find it very hard to interpret): The image below is this app (shown on the left) going back and forth between a homepage and a page with a listview.
0 kommentar(er)
