Databases
StackOverflow2013
Postsdbo
POiOS addSubview & removeFromSuperview causing memory leaks
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POiOS addSubview & removeFromSuperview causing memory leaks
    primarykey
    data
    text
    <p>I have the following issue:</p> <p>I have one instance from class that extends UIViewController class, in this class i am adding UIImage to UIImageView, and then adding the UIImageView to the self.view using this method "addSubview:" [self.view addSubview:imageView] and finally adding the self.view to the window using [[[UIApplication sharedApplication] keyWindow] addSubview:[self view]] , and when i click on a close button i am clearing the self.view (removing the subview "UIImageView") and removing the self.view from the window.</p> <p>now the issue is when i am using the same instance to add other UIImageView with other image, the first data is not freed from the memory even i have released them and removed them from the superview. the following code illustrates the problem.</p> <pre><code>- (void) setImageWithURL: (NSString *)url { NSData * imageData =NSData * imageData =[NSData dataWithContentsOfURL:[NSURL URLWithString:url]]; if (imageData) { UIImage *image = [[UIImage alloc]initWithData:imageData]; [[[UIApplication sharedApplication] keyWindow] addSubview:[self view]]; [self createViewWithImage:image]; [image release]; } -(void) createViewWithImage: (UIImage *) image{ [self.view setHidden:false]; UIImageView *imageView = [[UIImageView alloc] initWithImage:image]; [self.view addSubview:imageView]; [imageView release]; } // for removing the imageView when i click on close button -(void) closeView{ for (UIView *subView in self.view.subviews) { [subView removeFromSuperview]; } [self.view removeFromSuperview]; } </code></pre> <p>Note: I have used the xcode instruments to test the memory allocation.</p> <p>UPDATE: after more research .. it is not addSubview &amp; removeFromSuperview that make memory leaks.. its NSData. I dont why its not released from the memory. I have made some changes to test if its truly the NSData, i saved the image locally and set the image using two cases:</p> <pre><code>//Case 1: NSString *path = [[NSBundle mainBundle] pathForResource:@"image" ofType:@"png"]; NSData * imageData =[[NSData dataWithContentsOfFile:path]; image = [[UIImage alloc]initWithData:imageData]; //Case 2: NSString *path = [[NSBundle mainBundle] pathForResource:@"image" ofType:@"png"]; image = [[UIImage alloc] initWithContentsOfFile:path]; </code></pre> <p>I have found that case one makes memory leaks, while case 2 is clean.</p> <p>now UIImage cant take the image without using the NSData, and for some reason NSData is not released .. so how can i fix this problem !!!!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMoha Mhe
    1. USMoha Mhe
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COWhy aren't you using ARC? It will save you a lot of time when it comes to memory management.
      singulars
      1. POiOS addSubview & removeFromSuperview causing memory leaks
      1. USEli Ganem
    2. COApple suggested at WWDC that ARC will soon be the ONLY way to go. I strongly recommend you start using it.
      singulars
      1. POiOS addSubview & removeFromSuperview causing memory leaks
      1. USAdam Waite
    3. COI have used ARC. but the problem was exist.. so i have compiled it without arc to see where is the problem ..
      singulars
      1. POiOS addSubview & removeFromSuperview causing memory leaks
      1. USMoha Mhe
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload