Databases
StackOverflow2013
Postsdbo
POEXC_BAD_ACCESS message sent to deallocated instance, but I'm using ARC?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEXC_BAD_ACCESS message sent to deallocated instance, but I'm using ARC?
    text
    copied!<p>I've got an app that gets information from a SOAP web service and I want to display the results in a <code>UITableView</code>. </p> <p>I had a previous version of this app and I'm creating a new version to basically clean things up and get rid of a bunch of legacy code that's deprecated and no longer used.</p> <p>In the previous version, this worked well. In the new version, not so much.</p> <p>Basically, the current scenario is returning 3 strings that I'm trying to use as the basis for the data in my <code>UITableView</code>.</p> <p>I'm struggling with this issue because it's so stinkin' hard to track down <code>EXC_BAD_ACCESS</code> errors! </p> <p>(Parenthetically, if someone has a way to make the debug experience more like Visual Studio, I'd love to hear it! It's so frustrating to not have any idea which line caused the error, and also to not be able to look through my local variables at the time of the crash to see what's what. I've already added in the exception breakpoint, but that doesn't seem to do much.)</p> <p>Anyway, the line that's causing the error APPEARS to be:</p> <pre><code>return [[self Libraries] count]; </code></pre> <p>It occurs in <code>tableView:numberOfRowsInSection:</code>.</p> <p>The error message I get APPEARS to reference a string that should be stored in the <code>NSMutableArray</code> <code>[self Libraries]</code>.</p> <p>What's going on here?<br/> I'm using <em>ARC</em>, so shouldn't all of my memory management be correctly handled?<br/> I don't have any manual release statements in my code ANYWHERE!</p> <p>Please help me fix this!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

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