I'm trying to remove a UITabBarController from a window in my app by calling removeFromSuperview on the controller's view after adding it to the window previously. However when i do so and after it deallocates all the view controllers that are on the bar successfully, i get an EXC_BAD_ACCESS signal after an autorelease pool is drained. by method swizzling i've found out that it happens after something called UITableViewRowData has its dealloc method called. I'm wondering if there's a bug when the more view controller is attempting to be deallocated. Has anyone else ever run into this problem?
A:
You are most likely releasing something you shouldn't be, can't really say what without some sample code
Daniel
2009-08-07 23:39:01
Possibly, but i don't know what it could be because it seems that all the view controllers owned by the view are released before the crash happens. This app is relatively complex so it'd be difficult to provide a concise code sample.
Kevlar
2009-08-08 19:00:36
Are u using a tabarviewcontroller? If u are it's very possible that it release ur views for u and u don't need to do so
Daniel
2009-08-08 20:38:18