2013-08-16 27 views
2


我的应用程序不会在设备上崩溃。没有泄漏没有记忆警告。我幸福地生活着。但最近我正在用Instrument(Automation)做一些UI测试。 Boom Boom。应用程序崩溃后,使用它像8分钟。循环播放30次。它会持续崩溃,但持续时间不同,但都在同一个步骤。再次没有泄漏没有记忆警告。再次它不会在设备上崩溃(没有仪器)无论多久使用我的应用程序。

+每次它弹出一个特定的ViewController后崩溃。该视图控制器加载了东西(图像查看,播放和录制音频,从相册和相机拍摄照片) 这里是设备日志。

高度赞赏任何形式的帮助。iOS应用程序崩溃,只有从仪器运行(自动化)

Incident Identifier: 
CrashReporter Key: 
Hardware Model:  iPhone5,2 
Process:   My App [15196] 
Path:    
Identifier:  My App 
Version:   ??? (???) 
Code Type:  ARM (Native) 
Parent Process: launchd [1] 

Date/Time:  2013-08-16 12:48:10.814 +0200 
OS Version:  iOS 6.1.3 (10B329) 
Report Version: 104 

Exception Type: EXC_BAD_ACCESS (SIGSEGV) 
Exception Codes: KERN_INVALID_ADDRESS at 0x1208b319 
Crashed Thread: 6 

Thread 0 name: Dispatch queue: com.apple.main-thread 
Thread 0: 
0 libsystem_kernel.dylib   0x39be3e30 mach_msg_trap + 20 
1 libsystem_kernel.dylib   0x39be3fd0 mach_msg + 48 
2 CoreFoundation     0x319da2b6 __CFRunLoopServiceMachPort + 126 
3 CoreFoundation     0x319d8fd6 __CFRunLoopRun + 814 
4 CoreFoundation     0x3194c238 CFRunLoopRunSpecific + 352 
5 CoreFoundation     0x3194c0c4 CFRunLoopRunInMode + 100 
6 GraphicsServices    0x3552b336 GSEventRunModal + 70 
7 UIKit       0x338682b4 UIApplicationMain + 1116 
8 MyApp      0x0000531e 0x3000 + 8990 
9 MyApp      0x000052d4 0x3000 + 8916 

Thread 1 name: Dispatch queue: com.apple.libdispatch-manager 
Thread 1: 
0 libsystem_kernel.dylib   0x39be45d0 kevent64 + 24 
1 libdispatch.dylib    0x39b1fd22 _dispatch_mgr_invoke + 806 
2 libdispatch.dylib    0x39b1b374 _dispatch_mgr_thread + 32 

Thread 2 name: WebThread 
Thread 2: 
0 libsystem_kernel.dylib   0x39be3e30 mach_msg_trap + 20 
1 libsystem_kernel.dylib   0x39be3fd0 mach_msg + 48 
2 CoreFoundation     0x319da2b6 __CFRunLoopServiceMachPort + 126 
3 CoreFoundation     0x319d902c __CFRunLoopRun + 900 
4 CoreFoundation     0x3194c238 CFRunLoopRunSpecific + 352 
5 CoreFoundation     0x3194c0c4 CFRunLoopRunInMode + 100 
6 WebCore       0x37954390 RunWebThread(void*) + 440 
7 libsystem_c.dylib    0x39b4d0de _pthread_start + 306 
8 libsystem_c.dylib    0x39b4cfa4 thread_start + 4 

Thread 3: 
0 libsystem_kernel.dylib   0x39be3e30 mach_msg_trap + 20 
1 libsystem_kernel.dylib   0x39be3fd0 mach_msg + 48 
2 CoreFoundation     0x319da2b6 __CFRunLoopServiceMachPort + 126 
3 CoreFoundation     0x319d902c __CFRunLoopRun + 900 
4 CoreFoundation     0x3194c238 CFRunLoopRunSpecific + 352 
5 CoreFoundation     0x3194c0c4 CFRunLoopRunInMode + 100 
6 Foundation      0x322705be -[NSRunLoop(NSRunLoop) runMode:beforeDate:]  + 250 
7 MyApp      0x00020b0a 0x3000 + 121610 
8 Foundation      0x3231d22c __NSThread__main__ + 968 
9 libsystem_c.dylib    0x39b4d0de _pthread_start + 306 
10 libsystem_c.dylib    0x39b4cfa4 thread_start + 4 

Thread 4 name: com.apple.NSURLConnectionLoader 
Thread 4: 
0 libsystem_kernel.dylib   0x39be3e30 mach_msg_trap + 20 
1 libsystem_kernel.dylib   0x39be3fd0 mach_msg + 48 
2 CoreFoundation     0x319da2b6 __CFRunLoopServiceMachPort + 126 
3 CoreFoundation     0x319d902c __CFRunLoopRun + 900 
4 CoreFoundation     0x3194c238 CFRunLoopRunSpecific + 352 
5 CoreFoundation     0x3194c0c4 CFRunLoopRunInMode + 100 
6 Foundation      0x32299888 +[NSURLConnection(Loader)  _resourceLoadLoop:] + 304 
7 Foundation      0x3231d22c __NSThread__main__ + 968 
8 libsystem_c.dylib    0x39b4d0de _pthread_start + 306 
9 libsystem_c.dylib    0x39b4cfa4 thread_start + 4 

Thread 5 name: com.apple.CFSocket.private 
Thread 5: 
0 libsystem_kernel.dylib   0x39bf4594 __select + 20 
1 CoreFoundation     0x319de474 __CFSocketManager + 676 
2 libsystem_c.dylib    0x39b4d0de _pthread_start + 306 
3 libsystem_c.dylib    0x39b4cfa4 thread_start + 4 

Thread 6 Crashed: 
0 Foundation      0x3231d692 __NSFinalizeThreadData + 122 
1 CoreFoundation     0x319d6212 __CFTSDFinalize + 62 
2 libsystem_c.dylib    0x39b3feb8 _pthread_tsd_cleanup + 172 
3 libsystem_c.dylib    0x39b3fb8e _pthread_exit + 114 
4 libsystem_c.dylib    0x39b42ade _pthread_workq_return + 22 
5 libsystem_c.dylib    0x39b427f2 _pthread_wqthread + 362 
6 libsystem_c.dylib    0x39b42680 start_wqthread + 4 

Thread 7: 
0 libsystem_kernel.dylib   0x39bf4d98 __workq_kernreturn + 8 
1 libsystem_c.dylib    0x39b42ad6 _pthread_workq_return + 14 
2 libsystem_c.dylib    0x39b427f2 _pthread_wqthread + 362 
3 libsystem_c.dylib    0x39b42680 start_wqthread + 4 

Thread 8: 
0 libsystem_kernel.dylib   0x39bf4d98 __workq_kernreturn + 8 
1 libsystem_c.dylib    0x39b42ad6 _pthread_workq_return + 14 
2 libsystem_c.dylib    0x39b427f2 _pthread_wqthread + 362 
3 libsystem_c.dylib    0x39b42680 start_wqthread + 4 

Thread 9 name: AURemoteIO::IOThread 
Thread 9: 
0 libsystem_kernel.dylib   0x39be3e30 mach_msg_trap + 20 
1 libsystem_kernel.dylib   0x39be3fd0 mach_msg + 48 
2 AudioToolbox     0x314cdc80 AURemoteIO::IOThread::Run() + 104 
3 AudioToolbox     0x314d000c AURemoteIO::IOThread::Entry(void*) + 4 
4 AudioToolbox     0x3140d9f2 CAPThread::Entry(CAPThread*) + 294 
5 libsystem_c.dylib    0x39b4d0de _pthread_start + 306 
6 libsystem_c.dylib    0x39b4cfa4 thread_start + 4 

Thread 6 crashed with ARM Thread State (32-bit): 
r0: 0x0010f522 r1: 0x39700941  r2: 0x39e57e88  r3: 0x1f8dc028 
r4: 0x1208b2fd r5: 0x0000001c  r6: 0x00000000  r7: 0x04af9f18 
r8: 0x1f8dc028 r9: 0x007f8014  r10: 0x00000004  r11: 0x00000037 
ip: 0x39d4db30 sp: 0x04af9d50  lr: 0x31946eb7  pc: 0x3231d692 
cpsr: 0x20000030 
+0

你是否发现我面临同样的问题... –

+0

我会说不要惊慌,因为这只发生在自动化中。其次,当开发人员编写更多整洁的代码时,它就解决了。但我不知道它究竟如何解决这个问题。通过整洁的代码或它只是一个xCode仪器的bug,并更新它解决它,因为没有仪器,它不会发生,无论我使用这个应用程序多久。 - 干杯。 –

回答

1

EXC_BAD_ACCESS通常表示您正在向无效内存地址发送目标c消息。发生这种情况是因为您正在使用的对象已被释放。

使用NSZombieEnabled获取更多信息。 开始评论的东西。这是一个内存问题,找到有害的代码行。

+0

谢谢约翰。 NSZombie不适合我,因为当我在真实设备上进行自动化时,应用程序只会崩溃。关于评论的东西。我正在为此工作。仍然没有运气 –