search

appunite / CLCascade

Twitter-like cascade UI library
http://appunite.com/
Other
504 stars 67 forks source link

Memory deallocation crash (Bad Access) #4

Closed grgcombs closed 13 years ago

grgcombs commented 13 years ago

Start the cascade example app in portrait mode and select a few rows to stack up new tableview panels.

Now, rotate the interface to landscape and swipe a few panels off to the right in order to expose the very first panel.

Now select any row ... observe the crash.

The call stack (from top to bottom) looks like the following:

[UITableView _selectRowAtIndexPath:animated:scrollPosition:notifyDelegate:]
[ExampleTableViewController tableView:didSelectRowAtIndexPath:]
[CLViewController pushDetailViewController:animated:]
[CLCascadeNavigationController addViewController:sender:animated:]
[NSMutableArray removeObjectsInRange:]
[__NSArrayM removeObjectAtIndex:]
CFRelease
[ExampleTableViewController dealloc]
[CLTableViewController dealloc]
[CLViewController dealloc]
??
objc_msgSend

I tried doing a little error checking on line 229 of [CLCascadeNavigationController addViewController:sender:animated:] by including a check to make sure the index range was valid for the view controller array, but either I didn't get the conditions correct or that range wasn't the real problem.

emilwojtaszek commented 13 years ago

Done.

mysticvalley commented 12 years ago

Hey emilwojtaszek, can you please tell me how you solved this issue? I am also having same above issue in my iPad App. Thanks in advance, any word would be great help.