I ran into this when rapidly changing images in an uiimageview.
As always known, the user is always to blame.
After a few hours of endless pain, i figured out what was wrong.
Using object allocation tool from instruments, i saw that the memory was increasing rapidly until it cracked. I double checked by implementing :
- (void)applicationDidReceiveMemoryWarning:(UIApplication *)application
in my main.
This was, in my case at least , a memory management problem. I was using [Uiimage imagenamed.....] which is an autoreleased uiimage. That cannot be released by the user and it caused the specified problem. I fixed this by implementing allocation and release programatically on all of the objects in question.
Sample code where I update an uiimageview's image:
-(void) updateImage{
CGRect rect=CGRectMake(0, 0, 320, uiviewsimage.frame.origin.y);
NSObject *img2=CGImageCreateWithImageInRect(uiviewsimage.CGImage, rect);
UIImage *newImage = [[UIImage alloc] initWithCGImage:img2];
[img2 release];
[myImageView setFrame:rect];
[myImageView setImage:newImage];
[newImage release];
}`
Hope this helps someone. Cheers