Databases
StackOverflow2013
Postsdbo
POself.tableView.delegate = self and self.table.dataSource = self memory leak
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POself.tableView.delegate = self and self.table.dataSource = self memory leak
    primarykey
    data
    text
    <p>I have following codes, which have memory leak on device, could you please kindly help check it? Thanks.</p> <pre><code>@interface NewsListViewController : UIViewController&lt;UITableViewDataSource, UITableViewDelegate&gt; { @private UITableView *tableView; NSFetchedResultsController *fetchedResultsController; ...... } @property (nonatomic, retain, readonly) NSFetchedResultsController *fetchedResultsController; @end @implementation NewsListViewController { ...... - (void)dealloc { [fetchedResultsController release]; fetchedResultsController = nil; tableView.delegate = nil; tableView.dataSource = nil; [tableView release]; tableView = nil; [super dealloc]; } -(void)viewDidLoad { ...... tableView.delegate = self; // **leak here** tableView.dataSource = self; // **leak here** DemoAppDelegate *appDelegate = (DemoAppDelegate *)[UIApplication sharedApplication].delegate; [[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(handleSaveNotification:) name:NSManagedObjectContextDidSaveNotification object:appDelegate.managedObjectContext]; </code></pre> <p>[self fetch];</p> <pre><code>} - (void)fetch { </code></pre> <p>NSError *error = nil; BOOL success = [self.fetchedResultsController performFetch:&amp;error]; if (!success) { debugLog(@"Unhandled error performing fetch: %@", [error localizedDescription]); NSAssert1(0, @"Unhandled error performing fetch: %@", [error localizedDescription]); } [tableView reloadData];</p> <pre><code>} - (NSFetchedResultsController *)fetchedResultsController { </code></pre> <p>if (fetchedResultsController == nil) { NSFetchRequest *fetchRequest = [[[NSFetchRequest alloc] init] autorelease];</p> <p>DemoAppDelegate *appDelegate = (DemoAppDelegate *)[UIApplication sharedApplication].delegate; [fetchRequest setEntity:[NSEntityDescription entityForName:@"News" inManagedObjectContext:appDelegate.managedObjectContext]];</p> <p>fetchedResultsController = [[NSFetchedResultsController alloc] initWithFetchRequest:fetchRequest managedObjectContext:appDelegate.managedObjectContext sectionNameKeyPath:nil cacheName:@"NewsCache"];</p> <pre><code>} </code></pre> <p>return fetchedResultsController; }</p> <pre><code> - (void)handleSaveNotification:(NSNotification *)aNotification { </code></pre> <p>DemoAppDelegate *appDelegate = (DemoAppDelegate *)[UIApplication sharedApplication].delegate; [appDelegate.managedObjectContext mergeChangesFromContextDidSaveNotification:aNotification]; [self fetch]; }</p> <pre><code> - (UITableViewCell *)tableView:(UITableView *)table cellForRowAtIndexPath:(NSIndexPath *)indexPath { News *news = [fetchedResultsController objectAtIndexPath:indexPath]; // fill cell.label.text according to the news field value } @end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmobguang
    1. USmobguang
    plurals
    1. This table or related slice is empty.
    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. COWhat makes you think that this leaks? We need more code, and info about leaked objects.
      singulars
      1. POself.tableView.delegate = self and self.table.dataSource = self memory leak
      1. USEiko
 

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