LLDB crash

Thanks for the insight. I will try to explain a little more about what is happening at the point of failing...and to express my frustration that I can't even reproduce the problem outside of the hardened runtime. The application is processing MR images using a mix of our own code, in C# and a third-party MRI image processing suite, running in a docker/podman container. The application sets up the data so that podman can access it and then triggers a podman process to start its processing. The triggering happens by preparing a 'Process' object...like a command shell invocation. Like: podman exec In development, this all works perfectly on all platforms. In packaged form, it works on Windows...because Microsoft has nothing even close to the hardened runtime in their distribution model. On the Mac, it generates the crash log provided above. This leads me to believe that I need some sort of Entitlement but which one? The test loop time is around 30 minutes and I don't which one might be the culprit. A

Even I force set the invalid value to the CAMetalLayer's frame ( zero width and height)or bounds (zero width and height) or drawableSize ( zero or extreme large number ) 3 property, I can not local repro any crash in the my org's lab on dozens of various iPhone

Do you know why was the format changed to this new pair of JSON dictionaries, when it seems like you pretty much need to convert it back to the more readable table-style format in order to debug with it? When I read the article Interpreting the JSON format of a crash report, it links to Adding identifiable symbol names to a crash report, and that article requires the crash log to be in the old table-style format in order to extract the info needed to run the atos command, which seems to be the only way I could find to determine which function call and line number in my source code are being referenced.

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. In your feedback report, please include a sysdiagnose report and a small Xcode project that can be used to reproduce the problem showing the APIs you are trying to use. Here are directions for creating a sysdiagnose report: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=sysdiagnose if you can't include a Xcode project, then please include crash logs and a copy of your .app distribution files. Bug Reporting: How and Why? has tips on creating your bug report.

Hello, Creating the drawable appears to be causing an internal crash while rendering your video frames. It's difficult to say if it's the configuration of the drawable texture or something else like limited resources (memory). Try reproducing the issue while profiling with Instruments to see if you can find any additional clues. Otherwise, in order for us to investigate please send us a bug report using the Feedback Assistant. Include a full crash log and sysdiagnose taken when the issue occurs.

Hello @rockdong, Is there an error message logged prior to this crash that provides a description of the failure? --Greg

And another app. Tips is crashing as well. All three apps (Tips, Mail, Safari) crash at the same point in WebKit, loading user installed Fonts. I've tried emptying my ~/library/fonts folder but that didn't help either.

Hi Kevin, I have createed 2 bugs for the above: Title: Method needed to detect if the current device supports DriverKit Bug number: FB18661587 Title: Crash when attempting to call systemExtensions(forApplicationWithBundleID bundleID: String) on iPad Pro Bug number: FB18662136 Thanks for your help on these.

To be clear, the Xcode project (and workspace) format is not documented for third-party developers, so DTS doesn’t support tools that generate or modify these formats. As to how this this is involved in the problem you’re seeing, that’s hard to say. It could just be a red herring. However, the nature of unsupported things is that they can cause all sorts of weird behaviour, so it’s quite possible that this is a factor. Two things: If you create a small test project and add these packages to it directly, does the code still crash? Please post a crash report for one of these crashes. I wanna skim through it for anything obvious. See Posting a Crash Report for advice on how to get and post the file. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com