Crashes on Masking (M1 Max) - EXC_BAD_ACCESS in CameraRaw (SIGSEGV)

[kgdizainslv]

I am reporting a persistent crash in Lightroom Classic 15.1 on Apple Silicon (Mac Studio M1 Max). The application crashes immediately when using AI Masking (Subject/People) or the Brush tool.

Troubleshooting attempted:

Reset Preferences: Fixed it for 1 day, then crash returned.

GPU Acceleration set to OFF: CRASH PERSISTS.

This confirms it is NOT a GPU/Metal driver issue.

I have analyzed the Crash Report. The crash occurs specifically in the CameraRaw framework (Thread 75), throwing a Segmentation Fault (SIGSEGV) due to an invalid memory write attempt. This indicates a bug in how the Camera Raw engine handles memory/buffer allocation for masking on ARM64 architecture in this specific release.

Here is the relevant Stack Trace from the Crash Report: 

Process:             Adobe Lightroom Classic [16777]
Identifier:          com.adobe.LightroomClassicCC7
Version:             15.1 (15.1)
Code Type:           ARM-64 (Native)
Hardware Model:      Mac13,1 (Mac Studio M1 Max)
Exception Type:      EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype:   KERN_INVALID_ADDRESS at 0xffffffffffffff38
Termination Reason:  Namespace SIGNAL, Code 11, Segmentation fault: 11

Thread 75 Crashed:: Worker Thread
0   CameraRaw                       0x12a77b044 0x12a6c8000 + 733252
1   AgKernel                        0x101cc165c 0x101cb4000 + 54876
2   AgKernel                        0x101cd07c0 0x101cb4000 + 116672
3   AgKernel                        0x101cc19f0 0x101cb4000 + 55792
...
Thread 75 crashed with ARM Thread State (64-bit):
   esr: 0x92000044 (Data Abort) byte write Translation fault

Conclusion: The byte write Translation fault inside the CameraRaw binary confirms a buffer overflow or invalid pointer access within the masking engine logic itself. Please forward this to the engineering team for a hotfix.

MAC STUDIO M1 MAX - 32gb ram. LRC 15.1. MacOS 26.1 & 26.2

[Rikk Flohr: Photography]

As a test, if you create a new macOS User Account and then log in to this test account, do you continue to see the failure?

Additionally: 

We’ve reviewed the email address you use with this forum and found no crash reports in our system.

Did you see a crash dialog?

Do you use a different email address when filling out the crash report?

Was the crash dialog Adobe’s? Apple’s?