![]() In its early days in macOS, RunningBoard seems to have had its greatest role to play with Catalyst apps, which have common code across iPadOS and macOS, so are no strangers to life cycle management. ![]() But it’s also important for desktop systems, if you want to maintain good performance when you need it. This is most relevant for notebooks, to ensure that the excesses of individual apps can’t exhaust their battery. I believe that it was ported to macOS as part of the preparations for Apple silicon, where life cycle management is considered essential. RunningBoard was originally developed in iOS, to manage the life cycle of apps, and ensure that they can’t hog the more limited resources of Apple’s devices. It’s more than two years since I last looked at the details of RunningBoard, so this is a good time to revisit it in Monterey, and ask how it has the power to terminate apps like that? ![]() His original discussion and account in his blog article go into all the gory details. The ultimate cause of this appears to have been a housekeeping app, which in trying to free up disk space, pulled the rug from under running apps, and caused macOS to force those apps to quit, apparently out of the blue. Let me explain.ĭaniel Jalkut, developer of MarsEdit, the world’s best blog authoring app, was investigating reports of his app suddenly quitting, when he came across reference to RunningBoard, a new sub-system introduced from iOS to macOS Catalina. What’s more, they did it with a RunningBoard. They murdered my most-used third-party app, the same one I’m writing this article in, MarsEdit. I’m not sure which of the players in the game Cluedo/Clue is the housekeeper, but I’d like to report a murder, and they did it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |