Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your leak is here:</p> <pre><code>self.currentCars = [[NSMutableArray alloc] init]; self.expiredCars = [[NSMutableArray alloc] init]; </code></pre> <p>Assuming that you declared property accessores like this:</p> <pre><code>@property(nonatomic, retain) NSMutableArray *currentCars; @property(nonatomic, retain) NSMutableArray *expiredCars; </code></pre> <p>In my opinion, the best way to find leaks (other than using Instruments) is to keep track of the retain count manually.</p> <p>If you were to do that with for example <code>currentCars</code>, you would find your leak easily. Here is what happens:</p> <pre><code>self.currentCars = [[NSMutableArray alloc] init]; // The 'init' makes the retain count 1. // 'self.currentCars = ..' translates to the setCurrentCars: method. // You probably did not implement that method yourself, // but by synthesizing your property it is automatically implemented like this: - (void)setCurrentCars:(NSMutableArray *)array { [array retain]; // Makes the retain count 2 [currentCars release]; currentCars = array; } // In your viewWillDisappear: method [currentCars release], currentCars = nil; // Makes the retain count 1 so the object is leaked. </code></pre> <p>The solution is simple. Use this:</p> <pre><code>NSMutableArray *tempMutableArray = [[NSMutableArray alloc] init]; self.currentCars = tempMutableArray; [tempMutableArray release]; </code></pre> <p>A little sidenote. You shouldn't release your objects in <code>viewWillDisappear:</code>. The recommended place to do that is <code>dealloc</code>. So your code would be:</p> <pre><code>- (void)dealloc { [currentCars release], currentCars = nil; [expiredCars release], expiredCars = nil; [super dealloc]; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODoes this code leak?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRits
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODoes this code leak?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COCalls to `-init` don't change retain counts. The retain count is set to 1 (at least as far as we know) by the call to `-alloc`, though Apple advises thinking in terms of ownership rather than retain counts, since trying to calculate retain counts rests on assumptions that will not always prove to be correct.
      singulars
      1. PO
      1. USjlehr
    2. COAlso, it's not necessarily wrong to release objects in `-viewWillDisappear:` to decrease memory consumption as long as the underlying instance variables are set to `nil`, as the OP has done here. On the other hand, setting instance variables to `nil` in `-dealloc` is unlikely to be useful.
      singulars
      1. PO
      1. USjlehr
 

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