網站首頁 編程語言 正文
1、野指針問題
【EXC_BAD_ACCESS (SIGSEGV) / KERN_INVALID_ADDRESS]
Possible zombie in call: Function: objc_releaseParam 1: 0x157f2a740 Originated at or in a subcall of unknown, cannot find symb
如有以下崩潰棧可以懷疑是在dealloc
中直接或間接使用了@try{} @catch{}
2、崩潰棧
libobjc.A.dylib _objc_release() CoreFoundation -[__NSDictionaryI dealloc]() CoreFoundation -[NSException dealloc]() libobjc.A.dylib AutoreleasePoolPage::releaseUntil(objc_object**)() libobjc.A.dylib _objc_autoreleasePoolPop() ...... ......
3、場景復現代碼
#import "ViewController.h" @interface TestExpectionObj : NSObject @end @implementation TestExpectionObj - (void)dealloc { @try { [self setValue:@"test" forKey:@"testKey"]; } @catch (NSException *exception) { NSLog(@"%@", exception); } } @end @implementation ViewController - (void)viewDidLoad { [super viewDidLoad]; // Do any additional setup after loading the view. [TestExpectionObj new]; } @end
4、問題分析
在dealloc
使用try-catch
并觸發catch時,會生成NSException
對象,exception結構如下
exception : NSException { userInfo: NSDictionary { NSTargetObjectUserInfoKey = "<TestExpectionObj: 0x6000038ac3e0>"; } }
故exception
會強引用TestExpectionObj
對象,并且exception
一般都是類方法生成會自動加入到AutoreleasePool
,所以dealloc
執行完后TestExpectionObj
對象已經釋放(因為在dealloc
方法中在強引用當前對象沒法終止當前對象的釋放,引用計數增加與否已無意義),所以exception.userInfo
中的TestExpectionObj
對變成野對象。
當AutoreleasePool
到達周期釋放時就對調用release exception & userInfo,字典userInfo
釋放時會也會相應的釋放key/value,故NSTargetObjectUserInfoKey = "<TestExpectionObj: 0x6000038ac3e0>"
又調用一次release
,因為之前已經dealloc
完畢,所以這次就會觸發重復釋放崩潰引起野指針問題,
但如果exception
在TestExpectionObj
對象的dealloc
方法執行完之前釋放就不會出現問題。
5、上報可能引起野指針崩潰棧
#import <JRSwizzle/JRSwizzle.h> @implementation NSException (ExceptionTestSunztObj) + (void)load { static dispatch_once_t onceToken; dispatch_once(&onceToken, ^{ [self jr_swizzleMethod:NSSelectorFromString(@"dealloc") withMethod:@selector(intercept_dealloc) error:nil]; }); } - (void)intercept_dealloc { BOOL isContainDealloc = NO; NSMutableString *symblos = [NSMutableString string]; for (NSString *sym in self.callStackSymbols) { [symblos appendFormat:@"%@\n", sym]; if ([sym containsString:@" dealloc]"]) { isContainDealloc = YES; } } // 把 symblos上報給自己的APM平臺 [APM report:@"ttReportExceptionCallStackSymbols" withValue:symblos]; [APM report:@"ttReportExceptionReason" withValue:self.reason?:@"NULL"]; if (isContainDealloc) { // 本地log打印,需符號化 TTLocalLog("NSException:throws:dealloc:ttReport", { @"name": self.name?:@"", @"reason": self.reason?:@"", @"callStackSymbols": symblos }); // 延遲保證數據寫完在釋放 __unsafe_unretained NSException *demoSelf = self; dispatch_after(dispatch_time(DISPATCH_TIME_NOW, (int64_t)(1.0 * NSEC_PER_SEC)), dispatch_get_main_queue(), ^{ [demoSelf intercept_dealloc]; }); return; } [self intercept_dealloc]; } @end
注:在dealloc
中使用@try{} @catch{}
可能會引起難以排查的野指針崩潰
使用@try-@catch
后
[<TestExpectionObj 0x600000714220> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key testKey. ( 0 CoreFoundation 0x0000000102a93604 __exceptionPreprocess + 242 1 libobjc.A.dylib 0x0000000102943a45 objc_exception_throw + 48 2 CoreFoundation 0x0000000102a9329c -[NSException init] + 0 3 Foundation 0x00000001034f2354 -[NSObject(NSKeyValueCoding) setValue:forKey:] + 315 4 ExpectionDemo 0x00000001023cae52 -[TestExpectionObj dealloc] + 50 5 libobjc.A.dylib 0x00000001029417b7 _ZN11objc_object17sidetable_releaseEbb + 177 6 ExpectionDemo 0x00000001023caf58 -[ViewController viewDidLoad] + 72 7 UIKitCore 0x000000010f3ce3bc -[UIViewController _sendViewDidLoadWithAppearanceProxyObjectTaggingEnabled] + 88 8 UIKitCore 0x000000010f3d2dbf -[UIViewController loadViewIfRequired] + 1193 9 UIKitCore 0x000000010f3d319a -[UIViewController view] + 27 10 UIKitCore 0x000000010fbdb00a -[UIWindow addRootViewControllerViewIfPossible] + 305 11 UIKitCore 0x000000010fbda6fe -[UIWindow _updateLayerOrderingAndSetLayerHidden:actionBlock:] + 230 12 UIKitCore 0x000000010fbdb6d6 -[UIWindow _setHidden:forced:] + 409 13 UIKitCore 0x000000010fbee204 -[UIWindow _mainQueue_makeKeyAndVisible] + 47 14 UIKitCore 0x000000010fe605f6 -[UIWindowScene _makeKeyAndVisibleIfNeeded] + 202 15 UIKitCore 0x000000010ef0fb8f +[UIScene _sceneForFBSScene:create:withSession:connectionOptions:] + 1591 16 UIKitCore 0x000000010fb98fbd -[UIApplication _connectUISceneFromFBSScene:transitionContext:] + 1299 17 UIKitCore 0x000000010fb99471 -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 301 18 UIKitCore 0x000000010f613afe -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 355 19 FrontBoardServices 0x0000000107090cdd -[FBSScene _callOutQueue_agent_didCreateWithTransitionContext:completion:] + 415 20 FrontBoardServices 0x00000001070bd216 __94-[FBSWorkspaceScenesClient createWithSceneID:groupID:parameters:transitionContext:completion:]_block_invoke.180 + 102 21 FrontBoardServices 0x000000010709f0ef -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 209 22 FrontBoardServices 0x00000001070bcdf5 __94-[FBSWorkspaceScenesClient createWithSceneID:groupID:parameters:transitionContext:completion:]_block_invoke + 352 23 libdispatch.dylib 0x0000000103c0ba5b _dispatch_client_callout + 8 24 libdispatch.dylib 0x0000000103c0e93b _dispatch_block_invoke_direct + 295 25 FrontBoardServices 0x00000001070e3da3 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 30 26 FrontBoardServices 0x00000001070e3c99 -[FBSSerialQueue _targetQueue_performNextIfPossible] + 174 27 FrontBoardServices 0x00000001070e3dcb -[FBSSerialQueue _performNextFromRunLoopSource] + 19 28 CoreFoundation 0x0000000102a004a7 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 29 CoreFoundation 0x0000000102a0039f __CFRunLoopDoSource0 + 180 30 CoreFoundation 0x00000001029ff8ce __CFRunLoopDoSources0 + 340 31 CoreFoundation 0x00000001029f9f68 __CFRunLoopRun + 871 32 CoreFoundation 0x00000001029f9704 CFRunLoopRunSpecific + 562 33 GraphicsServices 0x00000001071e3c8e GSEventRunModal + 139 34 UIKitCore 0x000000010fb9765a -[UIApplication _run] + 928 35 UIKitCore 0x000000010fb9c2b5 UIApplicationMain + 101 36 ExpectionDemo 0x00000001023cb1be main + 110 37 dyld 0x00000001025e6f21 start_sim + 10 38 ??? 0x00000001091ce4fe 0x0 + 4447855870 )
這種崩潰信息使用NSSetUncaughtExceptionHandler()
是抓不到的
原文鏈接:https://juejin.cn/post/7141289369688047653
相關推薦
- 2022-11-01 使用react在修改state中的數組和對象數據的時候(setState)_React
- 2022-06-04 Jenkins安裝的時區問題分析解決_安裝教程
- 2022-04-03 基于QT5實現一個時鐘桌面_C 語言
- 2023-03-11 Golang跳轉語句continue與goto使用語法詳解_Golang
- 2022-07-16 遠程管理常用命令(ipconfig、ping等)
- 2022-12-10 React實現控制減少useContext導致非必要的渲染詳解_React
- 2022-01-14 2022年了--你還不會手寫promise? 完成promise的所有實現
- 2022-10-25 IDEA 安裝tomcat10創建servlet報404錯誤
- 最近更新
-
- window11 系統安裝 yarn
- 超詳細win安裝深度學習環境2025年最新版(
- Linux 中運行的top命令 怎么退出?
- MySQL 中decimal 的用法? 存儲小
- get 、set 、toString 方法的使
- @Resource和 @Autowired注解
- Java基礎操作-- 運算符,流程控制 Flo
- 1. Int 和Integer 的區別,Jav
- spring @retryable不生效的一種
- Spring Security之認證信息的處理
- Spring Security之認證過濾器
- Spring Security概述快速入門
- Spring Security之配置體系
- 【SpringBoot】SpringCache
- Spring Security之基于方法配置權
- redisson分布式鎖中waittime的設
- maven:解決release錯誤:Artif
- restTemplate使用總結
- Spring Security之安全異常處理
- MybatisPlus優雅實現加密?
- Spring ioc容器與Bean的生命周期。
- 【探索SpringCloud】服務發現-Nac
- Spring Security之基于HttpR
- Redis 底層數據結構-簡單動態字符串(SD
- arthas操作spring被代理目標對象命令
- Spring中的單例模式應用詳解
- 聊聊消息隊列,發送消息的4種方式
- bootspring第三方資源配置管理
- GIT同步修改后的遠程分支