84669 person learning
152542 person learning
20005 person learning
5487 person learning
7821 person learning
359900 person learning
3350 person learning
180660 person learning
48569 person learning
18603 person learning
40936 person learning
1549 person learning
1183 person learning
32909 person learning
1、app在ios8的机子上真机调试，在页面跳转后，在返回到上级界面，再次点击屏幕，就出现闪退.开启僵尸对象，打印信息如下：* -[_UIWebViewScrollView _systemGestureStateChanged:]: message sent to deallocated instance 0x3183a002、app在ios9 的机子上真机调试一切正常。
欢迎选择我的课程，让我们一起见证您的进步~~
Owner, I have also encountered this problem, but it has not been solved yet. Have you solved it now? Can you communicate with me?
Be extra careful when using delegate and datasource on iOS8.
Some delegate and datasource on iOS8 are declared using assign. If not released in time, it is easy to cause a crash.
It is recommended that wherever delegate is used, its display location should be set to nil in dealloc.
as
- (void)dealloc { _tableView.delegate = nil; _tableView.datasource = nil; _scrollView.delegate = nil; _gesture.delegate = nil; }
(void)dealloc{
_webView.delegate = nil;
}
viewWillDisappear 里写一句 [self.webView stopLoading];
viewWillDisappear
[self.webView stopLoading];
The problem was found because I referenced a third-party buckle and used the swizzle method to cause a memory leak.
Which third party does the poster use? Do you mind disclosing it? I have the same problem here...
After searching for 6 hours, I finally found which library caused it. . . UIScrollView+HeaderScaleImage! ! ! ! !
Check whether the UIScrollView category in your project has overridden the dealloc method
Using this UIScrollView+HeaderScaleImage, how to solve it
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Owner, I have also encountered this problem, but it has not been solved yet. Have you solved it now? Can you communicate with me?
Be extra careful when using delegate and datasource on iOS8.
Some delegate and datasource on iOS8 are declared using assign. If not released in time, it is easy to cause a crash.
It is recommended that wherever delegate is used, its display location should be set to nil in dealloc.
as
(void)dealloc
{
}
viewWillDisappear里写一句[self.webView stopLoading];The problem was found because I referenced a third-party buckle and used the swizzle method to cause a memory leak.
Which third party does the poster use? Do you mind disclosing it? I have the same problem here...
After searching for 6 hours, I finally found which library caused it. . . UIScrollView+HeaderScaleImage! ! ! ! !
Check whether the UIScrollView category in your project has overridden the dealloc method
Using this UIScrollView+HeaderScaleImage, how to solve it