URGENT: Corona Graphics Driver CRASHES - internal error on iPhone 6

I’m running daily build 2802.

I’ve had this same problem on an iPhone 6 and iPhone 6+, both running iOS v9+

My game is 95% complete, and it does take 20 minutes for this to happen - but it happens and is terrible. I would hate to imagine that I’ve spent a year and a half to make a game that will never be released because of this problem. PLEASE HELP!

Mar  2 14:44:11 iPhone kernel[0] <Notice>: AGXk: agxk_gl_context.cpp:597:process_hardware_command: void AGXGLContext::process_hardware_command(IOAccelCommandStreamInfo &):  Setting fContextError to kContextStateError @ /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleEmbeddedGPUDrivers/AppleEmbeddedGPUDrivers-75.11.5/Kernel/agxk_gl_context.cpp:597
Mar  2 14:44:11 iPhone kernel[0] <Notice>: The graphics driver has encountered internal error 0x0, 0xffffffff.
Mar  2 14:44:11 iPhone com.apple.xpc.launchd[1] (UIKitApplication:com.appname.rdgames[0x9f0b][2385]) <Notice>: Service exited due to signal: Segmentation fault: 11
Mar  2 14:44:11 iPhone SpringBoard[1906] <Warning>: HW kbd: Failed to set (null) as keyboard focus
Mar  2 14:44:11 iPhone SpringBoard[1906] <Warning>: Application ‘UIKitApplication:com.appname.rdgames[0x9f0b]’ crashed.
Mar  2 14:44:11 iPhone UserEventAgent[1874] <Warning>: 4079705678576: id=com.appname.rdgames pid=2385, state=0
Mar  2 14:44:11 iPhone mediaserverd[1876] <Notice>: ‘’ com.appname.rdgames(pid = 2385) setting DiscoveryMode = DiscoveryMode_None, currentDiscoveryMode = DiscoveryMode_None
Mar  2 14:44:11 iPhone diagnosticd[1936] <Error>: unable to find offset 0x83991804 in shared cache for arch ‘arm64’
Mar  2 14:44:11 iPhone ReportCrash[2460] <Notice>: platform_thread_get_unique_id matched 667992
Mar  2 14:44:11 iPhone ReportCrash[2460] <Notice>: Formulating report for corpse[2385] APP NAME
Mar  2 14:44:12 iPhone ReportCrash[2460] <Warning>: saved type ‘109_APP NAME’ report (4 of max 25) as /var/mobile/Library/Logs/CrashReporter/APP NAME_2016-03-02-144411_iPhone.ips
Mar  2 14:44:12 iPhone searchd[2459] <Warning>: ====^^^^ DuetExpert missing data, count -> people:8 applicationDeepLinks:0 applications:8 requests:1 missingAllDataRequests:0

i don’t think the following is related, because it’s about 30 seconds later.

Mar  2 14:44:46 iPhone dataaccessd[1975] <Notice>: 0x13561a190|EAS|Error|[ASPingTask 0x135569000, conn 0x13557c830, request 0x1355c3a70] connection died with error Error Domain=NSURLErrorDomain Code=-1005 “The network connection was lost.” UserInfo={NSUnderlyingError=0x1355d0ff0 {Error Domain=kCFErrorDomainCFNetwork Code=-1005 “The network connection was lost.” UserInfo={NSErrorFailingURLStringKey=https://outlook.office365.com/Microsoft-Server-ActiveSync?User=tlyndon@liberty.edu&DeviceId=L6Q7ACNMOT32H63UN6FS162HM0&DeviceType=iPhone&Cmd=Ping, NSErrorFailingURLKey=https://outlook.office365.com/Microsoft-Server-ActiveSync?User=tlyndon@liberty.edu&DeviceId=L6Q7ACNMOT32H63UN6FS162HM0&DeviceType=iPhone&Cmd=Ping, _kCFStreamErrorCodeKey=-4, _kCFStreamErrorDomainKey=4, NSLocalizedDescription=The network connection was lost.}}, NSErrorFailingURLStringKey=https://outlook.office365.com/Microsoft-Server-ActiveSync?User=tlyndon@liberty.edu&DeviceId=L6Q7ACNMOT32H63UN6FS162HM0&DeviceType=iPhone&Cmd=Ping, NSErrorFailingURLKey=https://outlook.office365.com/Microsoft-Server-ActiveSync?User=tlyndon@liberty.edu&DeviceId=L6Q7ACNMOT32H63UN6FS162HM0&DeviceType=iPhone&Cmd=Ping, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-4, NSLocalizedDescription=The network connection was lost.}
Mar  2 14:44:46 iPhone dataaccessd[1975] <Notice>: 0x13561a190|EAS|Error|ASPingTask failed: Error Domain=NSURLErrorDomain Code=-1005 “The network connection was lost.” UserInfo={NSUnderlyingError=0x1355d0ff0 {Error Domain=kCFErrorDomainCFNetwork Code=-1005 “The network connection was lost.” UserInfo={NSErrorFailingURLStringKey=https://outlook.office365.com/Microsoft-Server-ActiveSync?User=tlyndon@liberty.edu&DeviceId=L6Q7ACNMOT32H63UN6FS162HM0&DeviceType=iPhone&Cmd=Ping, NSErrorFailingURLKey=https://outlook.office365.com/Microsoft-Server-ActiveSync?User=tlyndon@liberty.edu&DeviceId=L6Q7ACNMOT32H63UN6FS162HM0&DeviceType=iPhone&Cmd=Ping, _kCFStreamErrorCodeKey=-4, _kCFStreamErrorDomainKey=4, NSLocalizedDescription=The network connection was lost.}}, NSErrorFailingURLStringKey=https://outlook.office365.com/Microsoft-Server-ActiveSync?User=tlyndon@liberty.edu&DeviceId=L6Q7ACNMOT32H63UN6FS162HM0&DeviceType=iPhone&Cmd=Ping, NSErrorFailingURLKey=https://outlook.office365.com/Microsoft-Server-ActiveSync?User=tlyndon@liberty.edu&DeviceId=L6Q7ACNMOT32H63UN6FS162HM0&DeviceType=iPhone&Cmd=Ping, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-4, NSLocalizedDescription=The network connection was lost.}
Mar  2 14:44:49 iPhone securityd[1943] <Error>:  SecOCSPSingleResponseCreate OCSPResponse: single response has extension(s).
Mar  2 14:44:49 iPhone securityd[1943] <Error>:  SecOCSPSingleResponseCreate OCSPResponse: single response has extension(s).
Mar  2 14:45:51 iPhone syslogd[1873] <Notice>: ASL Sender Statistics
 

Can you update to 2830 and try with that?

Rob

I just updated to 2830 and will let you know how it works out.

This bug appears to occur with version 2830, as reported by one of my testers.

With Xcode connected, you can save Crash Report. Can you please post this file here?

The console output above was in XCode. I would be happy to upload a crash report, but where and how is that done in XCode?

I’m not running the XCode simulator.Im running the game on my iPhone connected via USB cable.

@troylyndonhttps://developer.apple.com/library/prerelease/ios/recipes/xcode_help-crashes_organizer/ViewingCrashReports/ViewingCrashReports.html

  1. Providing crash logs can be very helpful. There are various ways of getting them off your device. One suggested by @Lerg would work.

Another is - connect your device, open Xcode. Click Window -> Devices (or press Command+Shift+2). In left pane select your device. Then click “View Device Logs” button under device information in the in main window area. There you can view crash logs. Locate latest crash of your game/app, right-click and export it.

  1. It is possible that you stumbled upon some of the bugs in Apples OpenGL ES driver. There was one introduced in iOS9. There may be workarounds, but provided info is far from enough to determine what is going on. But this is my wild guess, your console logs don’t really provide any leads to pinpoint specific it’s even hard to tell what crashed from it.

This problem has not yet been seen with Daily Build 2830. However, a new Graphics Driver on Android problem with 2830 has made any change of an Android release impossible, without help. Details at: https://forums.coronalabs.com/topic/62032-crash-adb-logcat-dcorona-13417-error-in-drawing-our-frame-surface-is-bad/

Can you update to 2830 and try with that?

Rob

I just updated to 2830 and will let you know how it works out.

This bug appears to occur with version 2830, as reported by one of my testers.

With Xcode connected, you can save Crash Report. Can you please post this file here?

The console output above was in XCode. I would be happy to upload a crash report, but where and how is that done in XCode?

I’m not running the XCode simulator.Im running the game on my iPhone connected via USB cable.

@troylyndonhttps://developer.apple.com/library/prerelease/ios/recipes/xcode_help-crashes_organizer/ViewingCrashReports/ViewingCrashReports.html

  1. Providing crash logs can be very helpful. There are various ways of getting them off your device. One suggested by @Lerg would work.

Another is - connect your device, open Xcode. Click Window -> Devices (or press Command+Shift+2). In left pane select your device. Then click “View Device Logs” button under device information in the in main window area. There you can view crash logs. Locate latest crash of your game/app, right-click and export it.

  1. It is possible that you stumbled upon some of the bugs in Apples OpenGL ES driver. There was one introduced in iOS9. There may be workarounds, but provided info is far from enough to determine what is going on. But this is my wild guess, your console logs don’t really provide any leads to pinpoint specific it’s even hard to tell what crashed from it.

This problem has not yet been seen with Daily Build 2830. However, a new Graphics Driver on Android problem with 2830 has made any change of an Android release impossible, without help. Details at: https://forums.coronalabs.com/topic/62032-crash-adb-logcat-dcorona-13417-error-in-drawing-our-frame-surface-is-bad/