Received memory warning. Level=1 please help me?

[Kenenth]

I am creating an app, and currently, everytime i run the app and go to the page that my app is on, when the page loads I get a warning in the debugger saying Received memory warning. Level=1. and then, later, when I try to do something in my game, it crashes saying something along the lines of

Program received signal: “0”.
Data Formatters temporarily unavailable, will re-try after a 'continue'. (Unknown error loading shared library "/Developer/usr/lib/libXcodeDebuggerSupport.dylib")


This has been really getting me frustrated. Is it possible that I have to many things in my nib file? I dont think it is. Because, I have 5 buttons, a slider, and 3 Images.I have seen much more complex games on Iphones that do not crash, and mine is very simple. What could be causing this?

[Duncan C]

Originally Posted by Kenenth

I am creating an app, and currently, everytime i run the app and go to the page that my app is on, when the page loads I get a warning in the debugger saying Received memory warning. Level=1. and then, later, when I try to do something in my game, it crashes saying something along the lines of

Program received signal: “0”.
Data Formatters temporarily unavailable, will re-try after a 'continue'. (Unknown error loading shared library "/Developer/usr/lib/libXcodeDebuggerSupport.dylib")


This has been really getting me frustrated. Is it possible that I have to many things in my nib file? I dont think it is. Because, I have 5 buttons, a slider, and 3 Images.I have seen much more complex games on Iphones that do not crash, and mine is very simple. What could be causing this?

Low memory warnings are a normal part of running an app under iOS. Your program needs to be written to respond to them correctly. Not handling a low memory warning can cause crashes, since low memory warnings do things like trigger view controllers aside from the front view controller to unload their views. Then the next time the view controller becomes the front view controller, its viewDidLoad method gets called again.

Low memory warnings can certainly also be caused by memory leaks or other programming problems. It's very hard to say what the cause is without a painstaking code review (which I'm not volunteering to do, mind you.)

Until you really understand the rules of Cocoa memory management and follow them religiously, it's easy to make mistakes that set you up for future crashes. That's my guess as to what's going wrong.