P: Crash on use of AI Settings (11562305) (11564853)

1. Version of the app Adobe Lightroom Classic 15.0 (Build 15.0)

2. Platform and OS version

• Platform: Mac mini M1 (Macmini9,1)

• OS: macOS 26.1 (Build 25B78) "Tahoe"

3. Basic steps to reproduce the problem Ai Culling is the culprit each time, a tiny bulk of images under 3,000 will crash every single time.  

4. Expected result and actual result

• Expected result: The AI task (Denoise, Lens Blur, etc.) should complete successfully, and Lightroom should remain stable.

• Actual result: The application enters an infinite recursive loop (over 8,154 calls to std::terminate), causing a stack overflow. The entire application freezes and crashes.

Full Crash Log: attached 

Incident 1: Stack Overflow Crash (LR-ERROR-110825A.txt)

• Primary Error: EXC_BAD_ACCESS (SIGILL) with an Exception Message: Thread stack size exceeded due to excessive recursion.

• Triggered Thread: Thread 64, labeled DLIF render thread.

• Technical Root Cause: The crash occurred due to an infinitely recurring loop within the program's low-level C++ exception handling (libc++abi.dylib, std::terminate(), __cxa_throw). When an initial exception occurred (likely within the rendering pipeline, possibly in CoreML/MPSGraph code), the program tried to handle or terminate it, which recursively called the termination routine over 8,154 times, consuming all stack memory and triggering a kernel protection failure (KERN_PROTECTION_FAILURE).

• Context: The involved frameworks (CoreML, Espresso, MetalPerformanceShadersGraph) confirm the initial event was triggered during an AI/GPU-accelerated task (such as Denoise, Masking, or AI-Culling/Face Detection). This recursive crash pattern often means a severe logic flaw in the library's cleanup or error-handling code when running accelerated tasks.

Incident 2: Segmentation Fault Crash (LR-ERROR-110825B.txt)

• Primary Error: EXC_BAD_ACCESS (SIGSEGV) with an Exception Subtype: KERN_INVALID_ADDRESS at 0xcc3a15b89210fa4c (possible pointer authentication failure).

• Triggered Thread: Thread 111, labeled Worker Thread.

• Technical Root Cause: This is a classic memory corruption error (Segmentation Fault). The thread tried to read or write data at an invalid, unmapped memory address (0xcc3a...). The address being a high, non-canonical address (0xcc3a...) that results in a Pointer Authentication failure (possible pointer authentication failure on ARM-64) points to a serious pointer corruption or an incorrect memory access during concurrent work.

• Context: The backtrace shows the crash originating deep within the CameraRaw library, specifically a routine that is called from the Lightroom Lua worker kernel (AgKernel and lua_pcall). Another thread (Thread 123) was actively in the process of freeing Metal/GPU resources (-[_MTLObjectWithLabel dealloc], -[IOGPUMetalResource dealloc], Espresso::net::~net()), suggesting a race condition where the GPU/AI thread (Thread 123) freed a resource (memory block, texture, CoreML network) while the Worker Thread (Thread 111) was still attempting to use it. This perfectly matches your hypothesis about a race condition in the AI/GPU processing pipeline.