I have a map view in my app in simulator works fine but when i test it on my ipod touch -2g 8gb sometimes it crashes could it be because my ipod is a bit old and don't have that much memory? in simulator everything works fine! and the leaks instrument shows no leaks!
Yes, that can be the case. The simulator has no memory limits that are relevant. Your old iPod does (though the 8GB is not the relevant number).
If you run the iPod connected to your computer and launch it from Xcode, does the crash happen, and does it have no stack trace? Then it's most likely memory.
Related
I have mac os mojave and xcode Version 10.1 (10B61). I try build unity3D game. I can successfully build it to iphone 5S device. But when I try submit up to App Store it is not working.
What exactly happens:
On step "fetching app store configuration" xcode freezes. In active monitor I see it as unresponsible application (or something like it). And XCode take almost all free RAM (4.5GB). After sometime (around 20 minutes) mac restart (I have problem with iMac, it restart when use too much RAM, I don't think it related to xcode)
Actually, if I wait long enough (more then 15 minutes) it is start working.
XCode require a lot of RAM + SWAP
Here's an answer for someone who stumbles upon this later, I just want to share what helped me. I also ran into the same problem while trying to distribute a Unity-built game with Xcode (also contains pods).
I work on a MacBook Air 2013 with only 4GB of RAM, so whenever I do anything with Xcode, I first close everything other than Xcode, Finder and Activity Monitor. As soon as I start whatever it is that usually freezes Xcode, I switch to Activity Monitor and track what's happening with the memory.
In the case of freezing while "Fetching App Store Configuration...", the problem appeared to be RAM, more precisely SWAP. I did not have enough memory available on my hard drive, which Xcode tried to use for SWAP and just... well, failed. So I cleaned up my hard drive and finally it went through very smoothly, but it occupied about 9GB of RAM at its peak (5.4GB in SWAP).
So just try to have enough memory available to feed the beast, observe what's happening in Activity Monitor and you should be good.
I am brand new to Apportable. I installed and am able to launch the sample Spin app on my Android device. However, after launch, my system is completely frozen and will not respond to any trackpad or keyboard touch. I hard booted and tried again with an iOS app I developed with the same results.
System:
MacBook Pro 15" Early 2011 running OSX 10.9
16GB RAM, 20 GB disk space available
Xcode 4.6
Any ideas why this is happening and what I can do to prevent it? Thanks!
Sometimes while copying the apk to the device, the USB driver gets blocked for a few seconds. If this is the same issue, then your system should return to normal pretty quickly (no more than five seconds on most machines).
If that isn't the case for you, you can try the following command:
MTP=no apportable load
If you still have the issue after that, something else is going on that I have never seen.
I had the same problem and MTP=no apportable load solved it for me.
I was recently trying to make my iOS 6 compatible app work with iOS 7 (noted still in beta). So i had my boss install iOS 7 on his iPhone 4S. We noticed that camera picker was slow and not responsive, and when we take a picture everything freezes. When i run the profile with memory allocations i notice that we have a really high memory usage : 160 MB. and btw we received a loot of memory warnings. So i tried running on the iPhone that still has ios6 and the maximum memory spike was 16 MB. Has anyone encountered this problem? Thank you
I do observe different Memory numbers on iOS 6 & iOS 7.
I have an app that makes use of openGL (a 3D viewer), and of AVFoundation (my own camera implementation, with AVCaptureDevice...)
I ran the app on iPhone 4S with iOS 6, and on iPhone 4 with iOS 7, my observations so far :
Allocations, Dirty & resident VM sizes reported by Instruments seem higher on iOS 7 than iOS 6 (50% to 100% higher)
BUT
I get much less Memory warning with iOS 7 (although I probably would have to repeat these tests to get more reliable results)
In iOS 7, apple introduce more restriction on memory allocation for single instance. If the single thread uses more memory it should crash.
This is not only related to native application but also related to hybrid app.
Ex: Google Maps getting crashed only in iOS 7, if it uses more memory. You can able to get more information in the below link.
Crashes in iOS7
So usually when EXC_BAD_ACCESS happens when I'm debugging my (largely c++ based) iphone app, I can go over to the GDB window and it'll show me the current stack.
However, for some reason, lately XCode freezes. This happened on both xcode 4 and xcode 3.
By freezing, I mean the wheel of death just spins non-stop, and after a while, the whole OS becomes unresponsive. On many occassions, I had to turn off the mac manually.
Could this be a case of trashing? I'm compiling a 300 files, 150k sloc project on an old 2009 mac mini with only 1GB memory. Could this be the reason? I'm pretty close to just buying a new mac mini with 8GB memory, but it seems a bit unlikely that a 2 year old computer can't handle simple compilation.
Considering I use 2GB of RAM without even loading Xcode, your 1GB could well be a problem.
It also could be a recursive bug that causes the debugger a hell of a lot of work by having an enormous stack trace.
It might be an problem in some infinite while/for loop. Try to set break-point in all such kind of piece of code where while/for loop are used.
I can't get my application running with Instruments. I tried running it in Xcode with Run › Start with Performance Tool. Instruments starts, iPod touch 2G gets stuck and restarts every time. I'm on OS X 10.6.2, Xcode 3.2.2 and using iOS SDK 3.2.1.
Running instruments adds a heavy load (both CPU and memory) to your device. The iPod 2G just may not be able to handle your app under load like this with instruments. Do you have a newer device that you can test your app with instruments to at least fix any leaks. If your app runs fine on the iPod without instruments it'll probably be ok.