iOS system panic, panic string Kernel data abort

Our user reported lately that their devices were rebooted automatically after using our app for more than 2 hours , at the beginnig I cannot , I never seen an app will make the iOS system get rebooted, until our user send me a video prove it what they said is true.


And after that I asked them for the panic-full logs in their devices which indicate the device was rebooted unusually, the log shows that it's exactly our app's process leads to the reboot, OMG, I got shocked...


Our app is a live broadcasting app, most of our users encountered the reboot problem are when they finished broadcasting a live for a long time (maybe more than 2 hours) and close the room button, another infomation is that we add WebRTC.framework to our app lately, Our user's devices and system version vary, so maybe there is no relation with these factors.


I reproduce this problem once on my iPhone 7P (I boradcasted for 2 hours, my phone rebooted exactly after I clicked the close button of my live room), and the panic log in my phone is very similar with logs from our users. Here is part of my log, I put the full on pastebin: https://pastebin.com/Hh9TqZgh


{

    "build":"iPhone OS 12.3.1 (16F203)",

    "product":"iPhone9,2",

    "kernel":"Darwin Kernel Version 18.6.0: Thu Apr 25 22:14:06 PDT 2019; root:xnu-4903.262.2~2/RELEASE_ARM64_T8010",

    "incident":"82BE9C5C-B6C3-40B4-98C7-B467ACEEF879",

    "crashReporterKey":"7800f8ead4380bbeae183732c167c3a212d0b0fe",

    "date":"2019-10-09 14:03:49.04 +0800",

    "panicString":"panic(cpu 0 caller 0xfffffff021e53bd0): Kernel data abort. (saved state: 0xffffffe050fbaf80)   x0: 0x0000000000000000  x1:  0x000f076700041104  x2:  0xfffffffffffffffb  x3:  0xffffffe04a4be81b   x4: 0x0000000000000000  x5:  0x0000000000000020  x6:  0x0000000000000000  x7:  0xfffffff0221fc940   x8: 0x139a6525663e0012  x9:  0x139a6525663e0012  x10: 0x0000000000000000  x11: 0x0200000010000860   x12: 0x0000000000000000 x13: 0x3a3a79726f6d654d  x14: 0x656e72654b746567  x15: 0x002928617461446c   x16: 0xfffffff021cb2df7 x17: 0x0000000000000020  x18: 0xfffffff021d31000  x19: 0xffffffe006609000   x20: 0xffffffe007192880 x21: 0x0000000281f9e760  x22: 0x0000000008600000  x23: 0x0000000000000006   x24: 0x000000000000000c x25: 0xffffffe0070b4600  x26: 0x0000000085020080  x27: 0x0000000000000018   x28: 0x0000000000000000 fp:  0xffffffe050fbb350  lr:  0xfffffff020f9ed74  sp:  0xffffffe050fbb2d0   pc:  0xfffffff020f9ed74 cpsr: 0x60400304         esr: 0x96000006          far: 0x0000000000000000 Debugger message: panic Memory ID: 0x1 OS version: 16F203 Kernel version: Darwin Kernel Version 18.6.0: Thu Apr 25 22:14:06 PDT 2019; root:xnu-4903.262.2~2/RELEASE_ARM64_T8010 KernelCache UUID: 2AEBFD081F36C4C81402573F19F4DEE7 Kernel UUID: 897227C4-A9D9-3E80-AA04-C1C2029A8430 iBoot version: iBoot-4513.260.81 secure boot?: YES Paniclog version: 12 Kernel slide:     0x000000001ac54000 Kernel text base: 0xfffffff021c58000 Epoch Time:        sec       usec   Boot    : 0x5d9c64c8 0x000468bc   Sleep   : 0x5d9d3a6c 0x000d0471   Wake    : 0x5d9d3aa5 0x00014f47   Calendar: 0x5d9d7819 0x0007c4af Panicked task 0xffffffe00634f2a0: 43873 pages, 21 threads: pid 339: EXXXLXXX Panicked thread: 0xffffffe001324000, backtrace: 0xffffffe050fba710, tid: 121839   lr: 0xfffffff021d661c4  fp: 0xffffffe050fba7a0   lr: 0xfffffff021e54538  fp: 0xffffffe050fba8e0   lr: 0xfffffff021d31610  fp: 0xffffffe050fba8f0   lr: 0xfffffff021d65768  fp: 0xffffffe050fbac60   lr: 0xfffffff021d65ae0  fp: 0xffffffe050fbaca0   lr: 0xfffffff021d65934  fp: 0xffffffe050fbacc0   lr: 0xfffffff021e53bd0  fp: 0xffffffe050fbae20   lr: 0xfffffff021e54c5c  fp: 0xffffffe050fbaf60   lr: 0xfffffff021d31610  fp: 0xffffffe050fbaf70   lr: 0xfffffff020f9ed74  fp: 0xffffffe050fbb350   lr: 0xfffffff020f9d590  fp: 0xffffffe050fbb3a0   lr: 0xfffffff020f9d39c  fp: 0xffffffe050fbb410   lr: 0xfffffff020f9c5f0  fp: 0xffffffe050fbb470   lr: 0xfffffff022217ee0  fp: 0xffffffe050fbb580   lr: 0xfffffff02221f8d4  fp: 0xffffffe050fbb710   lr: 0xfffffff021e2b128  fp: 0xffffffe050fbb820   lr: 0xfffffff021d49c90  fp: 0xffffffe050fbb9b0   lr: 0xfffffff021d5c17c  fp: 0xffffffe050fbbb40   lr: 0xfffffff021e54d28  fp: 0xffffffe050fbbc80   lr: 0xfffffff021d31610  fp: 0xffffffe050fbbc90   lr: 0x00000001a343b0f4  fp: 0x0000000000000000 ",

    "panicFlags":"0x2",

    "otherString":" ** Stackshot Succeeded ** Bytes Traced 357072 ** ",

    "memoryStatus":{

        "compressorSize":8413,

        "compressions":50291,

        "decompressions":21892,

        "busyBufferCount":0,

        "pageSize":16384,

        "memoryPressure":false,

        "memoryPages":{

            "active":68032,

            "throttled":0,

            "fileBacked":61496,

            "wired":24379,

            "purgeable":2883,

            "inactive":40858,

            "free":11191,

            "speculative":27437

        }

    }

........

}


I have no idea about what to do next to resolve this problem, any suggestions will help, thanks!


Replies

Kernel panics are always bugworthy. You should file a bug with whatever helpful info you have. At a minimum, include the panic log you have, but it’d be great if you could also include:

  • Steps to reproduce

  • A sysdiagnose log taken immediately after the panic caused a reboot

Please post your bug number, just for the record.

Looking at your panic log with internal tools, it looks like this is being triggered by the graphics accelleration subsystem. In my experience this is one of the most common causes of app-triggered panics. If you were using a low-level API like Metal directly, it’s possible that you might eb able to tiptoe around whatever causes this panic. However, if you’re using high-level APIs (I’m not familiar with the WebRFC framework, but it seems likely it’d be based on AVFoundation rather than Metal directly), your options are rather limited.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Thank you very much!


What you say reminds me a thing, when I run my project with Xcode 11, my app will crash when I start to broadcast, and this line get output in the console, this log is also related to Metal:


validateNewTexture:89: failed assertion `BytesPerRow of a buffer-backed texture with pixelFormat(MTLPixelFormatBGRA8Unorm) must be aligned to 64 bytes, found bytesPerRow(4976)'


When I disbale Metal API Validation in Debug options configuration, the crash disappeared.

I'll check where we use Metal incorrectly. Any suggestions or clues are appreciated. Thanks!

Any suggestions or clues are appreciated.

I’m not an expert on Metal, so apologies if this is obvious but…

Do these Metal API validation errors show up in the Runtime tab of the issue navigator (View > Navigators > Show Issue Navigator)? If so, that should give you a backtrace.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

I have committed a bug, bug number: FB7415440

(It's not easy for our users to press the buttons to generate diagnose log, so it's a few days late)

I’m not a developer, not even a nerd — but a user and I’m getting these panic events/bugs/crashes - just had one a little while ago, if this is any help. Apparently these are still happening. Thought someone might want to know — it didn’t say it was shared with Developers and the below was everything in the “log” or whatever it’s called.
I have lots of weird “bug types” on this iPad Pro 9.7.

Prior to this happening, I was just back and forth in a couple of things — in fact think I was in Safari when it happened. It says something about the Calendar but I wasn’t in the calendar, hadn’t had it up since earlier today. Anyway, I was closed down completely to a black screen, then the Apple logo came up, and then to passcode to sign in etc. I tried to send you the links to the 3 or so websites but they weren’t anything unusual and it wouldn’t let me include them. However, I went back to each and nothing happened so I don’t think it was the sites themself and they were all still up as was everything else I was working in which was nothing unusual. I don’t use any apps that don’t come through Apple. And I have to close down all apps at least once to a couple times a day from the “double click home button” screen so it wasn’t like tons of apps, sites, YT, etc had been up.
thanks Pam
plips71755@aol.com


===

"bugtype":"210","timestamp":"2020-12-15 21:32:09.00 -0500","osversion":"iPhone OS 14.2 (18B92)","incidentid":"7757EEF7-31FD-4CFD-88E9-2797E920CF3B"}
{
"build" : "iPhone OS 14.2 (18B92)",
"product" : "iPad6,4",
"kernel" : "Darwin Kernel Version 20.1.0: Fri Oct 30 00:34:16 PDT 2020; root:xnu-7195.42.3~1\/RELEASE
ARM64S8000",
"incident" : "7757EEF7-31FD-4CFD-88E9-2797E920CF3B",
"crashReporterKey" : "a8a0936a78bafd86ab3060d657fee48859aae5d6",
"date" : "2020-12-15 21:32:09.64 -0500",
"panicString" : "panic(cpu 0 caller 0xfffffff027168a80): Kernel data abort. at pc 0xfffffff026b2c174, lr 0xfffffff026bec124 (saved state: 0xfffffff0196d3600)\n\t x0: 0xfffffff90e1ea094 x1: 0xfffffff0afe7c000 x2: 0xfffffff01782c000 x3: 0x0000000000002374\n\t x4: 0xfffffff026a346e0 x5: 0xfffffff01782e000 x6: 0xfffffff0196d3d38 x7: 0xfffffff0196d3d34\n\t x8: 0x000000027cf43d7c x9: 0xfffffff9c52bcd88 x10: 0xfffffff90e1ea4a0 x11: 0xfffffff01782fffe\n\t x12: 0x0000000000002000 x13: 0x00000000cd005a9d x14: 0xffffffff2e5cb83d x15: 0x0000000000000000\n\t x16: 0x0000000000004000 x17: 0xfffffff026ae0000 x18: 0xfffffff026b31000 x19: 0xfffffff0196d3a54\n\t x20: 0x0000000000000000 x21: 0x0000000001800c44 x22: 0xfffffff0271c3000 x23: 0xfffffff0afe7c000\n\t x24: 0x0000000000002374 x25: 0x0000000000000000 x26: 0x0000000000000006 x27: 0xfffffff27a8b4e90\n\t x28: 0x0000000000002374 fp: 0xfffffff0196d3a10 lr: 0xfffffff026bec124 sp: 0xfffffff0196d3950\n\t pc: 0xfffffff026b2c174 cpsr: 0x20000204 esr: 0x96000006 far: 0xfffffff9c52bcd88\n\nDebugger message: panic\nMemory ID: 0x6\nOS release type: User\nOS version: 18B92\nKernel version: Darwin Kernel Version 20.1.0: Fri Oct 30 00:34:16 PDT 2020; root:xnu-7195.42.3~1\/RELEASE
ARM64S8000\nKernelCache UUID: 1AF8E058F1FE09FAFD3CE89189C53847\nKernel UUID: B5DBFC7A-125C-3AC3-9772-2C62769F5BE3\niBoot version: iBoot-6723.42.3\nsecure boot?: YES\nPaniclog version: 13\nKernel slide: 0x000000001fa2c000\nKernel text base: 0xfffffff026a30000\nmachabsolutetime: 0xf74661d127c\nEpoch Time: sec usec\n Boot : 0x5fbe5a08 0x000999af\n Sleep : 0x5fd9397a 0x000df5d9\n Wake : 0x5fd9397b 0x000d3991\n Calendar: 0x5fd97191 0x000e762b\n\nPanicked task 0xfffffff278f00000: 846 pages, 7 threads: pid 33033: duetexpertd\nPanicked thread: 0xfffffff2782769c8, backtrace: 0xfffffff0196d2e30, tid: 4283320\n\t\t lr: 0xfffffff026b6b85c fp: 0xfffffff0196d2e70\n\t\t lr: 0xfffffff026b6b6b8 fp: 0xfffffff0196d2ee0\n\t\t lr: 0xfffffff026c75e6c fp: 0xfffffff0196d2fa0\n\t\t lr: 0xfffffff026b31594 fp: 0xfffffff0196d2fb0\n\t\t lr: 0xfffffff026b6b3ec fp: 0xfffffff0196d3330\n\t\t lr: 0xfffffff026b6b3ec fp: 0xfffffff0196d3390\n\t\t lr: 0xfffffff0271680f0 fp: 0xfffffff0196d33b0\n\t\t lr: 0xfffffff027168a80 fp: 0xfffffff0196d3520\n\t\t lr: 0xfffffff026c763b4 fp: 0xfffffff0196d35e0\n\t\t lr: 0xfffffff026b31594 fp: 0xfffffff0196d35f0\n\t\t lr: 0xfffffff026bec124 fp: 0xfffffff0196d3a10\n\t\t lr: 0xfffffff026be5c14 fp: 0xfffffff0196d3ab0\n\t\t lr: 0xfffffff026be5704 fp: 0xfffffff0196d3af0\n\t\t lr: 0xfffffff026be815c fp: 0xfffffff0196d3b30\n\t\t lr: 0xfffffff026bf5ab0 fp: 0xfffffff0196d3dc0\n\t\t lr: 0xfffffff026c76558 fp: 0xfffffff0196d3e30\n\t\t lr: 0xfffffff026c75f18 fp: 0xfffffff0196d3ef0\n\t\t lr: 0xfffffff026b31594 fp: 0xfffffff0196d3f00\n\n",
"panicFlags" : "0x40",
"binaryImages" : [],
"notes" : ["Source: EmbeddedDevicePanicLogNamespace"]
}


===
There was another event right after.

{"app
name":"PerfPowerServicesSignpostReader","timestamp":"2020-12-15 07:21:43.00 -0500","appversion":"1.0","sliceuuid":"202B8282-CC0E-347D-845D-081EA486DA8A","adamid":0,"buildversion":"1","bundleID":"com.apple.PerfPowerServicesSignpostReader","sharewithappdevs":1,"isfirstparty":1,"bugtype":"202","osversion":"iPhone OS 14.2 (18B92)","incidentid":"160915ED-CDD8-462D-8F15-4FD6B9AD0F37","name":"PerfPowerServicesSignpostReader"}
Date/Time: 2020-12-15 07:20:04.211 -0500
End time: 2020-12-15 07:21:42.995 -0500
OS Version: iPhone OS 14.2 (Build 18B92)
Architecture: arm64
Report Version: 32
Incident Identifier: 160915ED-CDD8-462D-8F15-4FD6B9AD0F37
Share With Devs: Yes

Data Source: Microstackshots
Shared Cache: 237960AE-A74B-3293-A9CC-82429F651718 slid base address 0x1af874000, slide 0x2f874000

Command: PerfPowerServicesSignpostReader
Path: /System/Library/PrivateFrameworks/PowerlogCore.framework/XPCServices/PerfPowerServicesSignpostReader.xpc/PerfPowerServicesSignpostReader
Identifier: com.apple.PerfPowerServicesSignpostReader
Version: 1.0 (1)
Parent: UNKNOWN [1]
PID: 32306

Event: cpu usage
didn’t send whole thing..

======


how i can fix my issue Apple tristar2:could not find system ID: bad IPC message ID b1170f0240