2012-09-27 85 views
0

偶尔,我看到崩溃免受来自-deallocSPTrack坠毁SPTrack的dealloc

Exception Type: EXC_BAD_ACCESS (SIGSEGV) 
Exception Codes: KERN_INVALID_ADDRESS at 0xb1e8ded2 
Crashed Thread: 13 

Thread 0 name: Dispatch queue: com.apple.main-thread 
Thread 0: 
0 libsystem_c.dylib    0x39bb8d5c memset$VARIANT$CortexA9 + 100 
1 CoreFoundation     0x35e1a7fc __CFAllocateObjectArray + 176 
2 CoreFoundation     0x35d62118 _CFXNotificationRemoveObservers + 420 
3 Foundation      0x33834490 -[NSNotificationCenter removeObserver:name:object:] + 228 
4 MyAppName      0x00179fd0 -[SPTrack dealloc] (SPTrack.m:291) 
5 MyAppName      0x0017993a __destroy_helper_block_141 (SPTrack.m:223) 
6 libsystem_blocks.dylib   0x352adab0 _Block_release + 220 
7 libdispatch.dylib    0x34b064b4 _dispatch_client_callout + 20 
8 libdispatch.dylib    0x34b0b1b8 _dispatch_main_queue_callback_4CF$VARIANT$mp + 220 
9 CoreFoundation     0x35de9f36 __CFRunLoopRun + 1286 
10 CoreFoundation     0x35d5ceb8 CFRunLoopRunSpecific + 352 
11 CoreFoundation     0x35d5cd44 CFRunLoopRunInMode + 100 
12 GraphicsServices    0x362992e6 GSEventRunModal + 70 
13 UIKit       0x3713b2fc UIApplicationMain + 1116 
14 MyAppName      0x0005e986 main (main.m:14) 
15 MyAppName      0x0001d8e4 start + 36 

这是在SPTrack对#291:

[[NSNotificationCenter defaultCenter] removeObserver:self name:SPSessionDidUpdateMetadataNotification object:self.session]; 

当我把这通常发生应用程序从后台返回。

任何想法可能是什么原因?它是否试图多次删除观察者?或者self.session无效? (使用调试器一直无法捕捉到。)

+1

这看起来像一个错误,除非你正在做一些超级疯狂的事情。我向CocoaLibSpotify的'dev'分支添加了一个提交,如果您的理论是真实的(这听起来像是一个合理的理论),它使它更加强大。正如你所说,如果没有完整的跟踪,很难进行调试。我会留意它的! – iKenndac

+0

谢谢。我会挑选承诺并看看它是否会消失。 –

+0

自从我根据补丁更新后,还没有看到此错误! –

回答