- Home /
Memory related error on iOS 7
Hi:
I have an app developed with the following:
xCode 4.6.3
Unity 4.1.5f1
Several external plugins like Prime31 social, Prime31 IAP, Open Source Burstly integration, etc
I have access to upload apps to testflight and download them to some of our company devices. We have an iPad 2 with iOS 7.0.2 installed and when I try to run the app on that device, I get an error. I managed to get the error from the logs and here's the important part of the logs:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: ' NSAllocateMemoryPages(1380206665) failed'
So I checked my xCode output and when the app is starting running while connected to a device I get this error.
Completed reload, in 0.176 seconds voodudeV2(29079,0x3d5b2b88) malloc: mmap(size=1380208640) failed (error code=12) error: can't allocate region *** set a breakpoint in malloc_error_break to debug
However, for non iOS 7 devices, application runs perfectly (even with that error on xCode console, the app does not feel laggy). Is there any way to solve this issue without having to upgrade my dev tools?, I'm very close to a final delivery and I'm afraid of having tons on compatibility issues when migrating either Unity or xCode. I researched a lot about this and I manage to know that it is, indeed a memory issue (weird that iOS 6.x devices allow the app to run). So I started doing profilers on Unity and adding instrumentation to xcode and I'm attaching some of the screenshots.
I have other 2 screenshots, 1 that compares my app with some of the ones that are runnig at the same time, and another one for my profiler, but could now load them. I can send them if anybody want them. Do you know a work around that could allow me to get rid of these issues without upgrading?
Thanks a lot.
I would suggest upgrading both Xcode and Unity to the latest versions, a lot of stuff happened in iOS 7, you can't expect earlier apps to run without errors, and trying to fix those ins$$anonymous$$d of just upgrading is probably unfeasible in the long run.
thanks a lot for the suggestion... I will migrate both tools and check if that fixes the problem.