ios -[MTMeViewController scrollViewDidScroll:]: message sent to deallocated instance 0x7fc0f6f2
2015-04-17 10:29
423 查看
这bug，估计很多人能遇到
原因：scrollView滚动还没结束就释放了delegate
解决办法：
原因：scrollView滚动还没结束就释放了delegate
解决办法：
- (void)dealloc{
self.youScrollView.delegate =nil;
}
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- iOS [MTMeViewController scrollViewDidScroll:]: message sent to deallocated instance
- [****ViewController scrollViewDidScroll:]: message sent to deallocated instance 0x12d6c22f0
- -[xxxViewController scrollViewDidScroll:]: message sent to deallocated instance 0x7fc04
- [HelpViewController respondsToSelector] message sent to deallocated instance
- [****ViewController respondsToSelector:]: message sent to deallocated instance
- iOS [xxxxController respondsToSelector:]: message sent to deallocated instance 0x1310293e0崩溃问题
- [****ViewController respondsToSelector:]: message sent to deallocated instance
- [**ViewController respondsToSelector:]: message sent to deallocated instance崩溃问题解决方法
- delegate---[ViewController respondsToSelector:]: message sent to deallocated instance 0x7f84
- [****ViewController respondsToSelector:]: message sent to deallocated instance
- ViewController respondsToSelector:]: message sent to deallocated instance
- UITextField textInputView: message sent to deallocated instance
- *** -[AlwayedDownVC tableView:canEditRowAtIndexPath:]: message sent to deallocated instance 0x17a971
- iOS开发 message sent to deallocated instance问题解决
- ios message sent to deallocated instance 重复release 内存问题
- Xcode做ios开发时 message sent to deallocated instance问题的解决方法(gdb和lldb)
- tableView滑动删除返回错误 [ tableView:canEditRowAtIndexPath:]:message sent to deallocated instance
- iOS内存错误EXC_BAD_ACCESS的解决方法(message sent to deallocated instance)
- iOS内存错误EXC_BAD_ACCESS的解决方法(message sent to deallocated instance)
- iOS之message sent to deallocated instance与EXC_BAD_ACCESS类错误