Bug Report

Description

The Problem:
The ReportCrash daemon process has been running at 98.9% CPU. It appears to be stuck processing crash reports from the "Status" app (bundle ID: app.status.mobile, version 2.36.1).

Root Cause:
The Status app is crashing repeatedly with the same error:

• Exception: EXC_BAD_ACCESS (SIGSEGV) - KERN_INVALID_ADDRESS at 0x0000000000000028
• This is a null pointer dereference - the app is trying to access memory at offset 0x28 (40 bytes) from a null pointer
• The crash occurs on the main thread with deep recursion involving Objective-C metaclass lookups

The crash report shows a recursion pattern that likely caused the ReportCrash daemon to get stuck while symbolizing the extremely deep stack trace.

Immediate Fix:
Nuked this app from my system.

Platform Context

Update: The bundle ID app.status.mobile indicates this was the iOS build of Status running on an Apple Silicon Mac via macOS's native iOS app compatibility — not the dedicated desktop build (which uses bundle ID im.Status.NimStatusClient). I was not aware I had the iOS version installed on my Mac.

However, the crash occurs in NativeSwipeHandlerItem_macos.mm and NativeIndicatorItem_macos.mm, which are in the shared ui/StatusQ/ library and compiled into both the mobile and desktop macOS builds. The underlying use-after-free is a genuine code defect that could affect either build. See the proposed fix in the comments and PR #19921.

Additional Information

• Status version: 2.36.1
• Bundle ID: app.status.mobile (iOS build running on macOS via Apple Silicon compatibility)
• Operating System: macOS (Darwin 25.2.0, Apple Silicon arm64)