Databases
StackOverflow2013
Postsdbo
PONSJSONSerialization leaks in Callback Block
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONSJSONSerialization leaks in Callback Block
    primarykey
    data
    text
    <p>I'm trying to use Blocks as callbacks for an API request via the method below. This method takes a Block that is nested in this method's Block. It works... BUT, </p> <p>If an Object that has called this method is dealloced, NSJSONSerialization dumps out a massive memory leak. It's all good while everything is running. The leak only happens after the requesting object is gone. The leaks are nearly all NSPlaceHolder types.</p> <p>I'm at my wits end and any ideas are greatly appreciated!</p> <pre><code> - (void)sendRequestUsingNSURLConnectionWith:(NSURLRequest *)request andCallback:(void (^)(id))handler { __block __typeof__(self)blockSelf = self; // CL: build a block to be run asynchronously ApiClientCallback handleResponse = [[^(NSURLResponse *response, NSData *data, NSError *error) { id results = nil; // CL: http errors would be caught here. if (error) { NSLog(@"[%@ %@] HTTP error: %@", NSStringFromClass([blockSelf class]), NSStringFromSelector(_cmd), error.localizedDescription); results = error; } else { // CL: parse the JSON NSError *jsonError = nil; NSError *apiError = nil; if (data) { results = [NSJSONSerialization JSONObjectWithData:data options:NSJSONReadingMutableContainers error:&amp;jsonError]; } else { results = nil; } // CL: json errors would be caught here. if (jsonError) { NSLog(@"[%@ %@] JSON error: %@", NSStringFromClass([blockSelf class]), NSStringFromSelector(_cmd), error.localizedDescription); results = error; } // CL: Check for API errors. else if ([blockSelf checkApiErrorCode:results error:&amp;apiError]) { //CL: if there's an error make the NSError object the result. if (apiError) results = apiError; } } // CL: Send result to the completion block of the requesting object handler(results); } copy] autorelease]; [NSURLConnection sendAsynchronousRequest:request queue:self.opQueue completionHandler:handleResponse]; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGnarlyDog
    1. USGnarlyDog
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PONSJSONSerialization leaks in Callback Block
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PONSJSONSerialization leaks in Callback Block
      1. This table or related slice is empty.
      1. VTUndeletion
    1. COPlease explain "NSJSONSerialization dumps out a massive memory leak"
      singulars
      1. PONSJSONSerialization leaks in Callback Block
      1. UShooleyhoop
    2. COI've found the issue and I'm utterly embarrassed at what the cause was. The requesting object that was causing the leak was a subclass of another object. I realized that I actually forgot to include [super dealloc] in the subclass. The subclass has just a couple properties being filled by the request while the super has about 15. For testing I was running the request many times before dealloc, thus the large leak. Doh!
      singulars
      1. PONSJSONSerialization leaks in Callback Block
      1. USGnarlyDog
    3. COYou should get a warning if you miss a [super dealloc] if you don't you might want to check your build settings
      singulars
      1. PONSJSONSerialization leaks in Callback Block
      1. UShooleyhoop
 

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