UIViewTableController: "EXC_BAD_ACCESS" When Scrolling Up/Down Past the Max Position of the Table

Question

I received an EXC_BAD_ACCESS when I try scroll up past the top or scroll down past the max position of the table view. This does not happen when tableview is empty but as soon as I add data to table cell and try to scroll up or down to far, I get an "EXC_BAD_ACCESS".

Is there a way to prevent the user from scrolling too far?

Answer 1

The problem isn't that the user is scrolling to far, the problem is that you are giving the table bad row indexes. The table believes it is larger than it actually has data for.

Check what you return from – numberOfSectionsInTableView: and –tableView:numberOfRowsInSection:. Those methods are where your problem most likely arises from.

Answer 2

Hi! Once i had also a problem like this! maybe something is wrong with your deallocation, that means you release any objects too fast! I can't tell you exactly what's wrong, you should post some code, especially the cellForRowAtIndexPath method. So far, check out this method on your own and try to find any dealloc problems.

Answer 3

Thanks a lot to @burki. In case anyone is having the same issue I solved it by removing 'autorelease' from my dequeueReusableCellWithIdentifier when I was using a custom cell type.