Among the latter is an active subsystem to replace an old service assertiond, which can cause apps to unexpectedly terminate – to you and me, crash – in both macOS 10.15 and iOS 13: RunningBoard. A post on Howard Oakley’s blog, “ RunningBoard: a new subsystem in Catalina to detect errors“, includes a particularly succinct description of the eponymous OS subsystem (emphasis mine):Ĭatalina brings several new internal features, a few of which have been documented, but others seem to have slipped past silently. However, Searching instead for just “RunnningBoard” offered a glimmer of hope. Searching for this results in only a few scant links, all related to Apple’s open source Darwin kernel. The other thing that jumped out at me from the log was the term “OS_REASON_RUNNINGBOARD”. Searching for the term yielded pertinent results like this post about Apple Mail and Safari “suddenly quitting.” Unfortunately, they all seem to be scratching their heads as much as I am. Here we have a message asserting that MarsEdit was terminated, on purpose, and better still, it includes an explanation! As far as explanations go, “CacheDeleteAppContainerCaches” is not much of one, but it did give me something to go on. 09:15:22.088718 (gui/501/4.384452971.384452977 ) : exited with exit reason (namespace: 15 code: 0xbaddd15c) - OS_REASON_RUNNINGBOARD | Yet even with this wealth of information, I was stymied. Open it up and see the wealth of information about nearly every aspect of the system. A few minutes later the report will be revealed in the Finder: a probably quite large zip archive. You’ll see the screen flash, an indication the system is starting to collect the reports. If you’re curious, the easiest way to grab one of these on any Mac is to simply press the Control, Option, Command, Shift, and “.” (period) keys at once. When I started to feel bad about asking Manton to try this, that, and the other thing, I finally asked if he could send me a “sysdiagnose” report. I wrote a question in the Apple Developer Forums, which turned into a kind of de facto diary as I pursued the issue. I put “crash reports” in quotes above, because although my in-app crash reporter notices the app abruptly terminates, the system doesn’t create any obvious artifacts. I’ve been peppering him with questions about the issue for weeks, while he stoicly puts up with the behavior.Įven with the assistance of a highly technical friend who can reproduce the issue at will, I had thrown my arms up in despair several times. Luckily, one of these users is my good friend and colleague, Manton Reece. The issue is most prevalent in MarsEdit, where I have a handful of users who run into the issue multiple times per day. For months now, I have been scratching my head over a small but persistent number of “crash reports” affecting a few of my apps.
#MACBOOK APP MARSEDIT ZIP#
#MACBOOK APP MARSEDIT MAC#
0 kommentar(er)
