Skip to main content
Cerezine
Known Participant
November 21, 2024

Photoshop 26.1 Crashing With Remove Tool

  • November 21, 2024
  • 24 replies
  • 4448 views

The new Photoshop 26.1 crashes when using the Remove Tool. More specifically, when the "Removing Area" loading bar appears, the application closes before it completes. I tested with the AI mode both "on" and "off", and the issue occurred in both cases. The crash is not immediate, as the tool sometimes works without problems, but the error has been consistently recurring across multiple files.
I'm running Photoshop on MacOs Sequoia with a M2 Mac. On preferences, changing the Remove Tool Processing from "Faster" to "More Stable" didn't make any difference on the issue.

24 replies

Known Participant
December 11, 2024

Just a headsup. I switched to the latest Photoshop Beta version (26.3.0), and so far have not had any crashes. Fingers crossed it stays that way.

Participant
December 11, 2024

Same thing here!!! :(( 

Participant
December 11, 2024

I'm having the same problem.  I boosted my Memory usage allowance and Cache levels and that seemed to resolve it on my end.  

Jqqerry
Inspiring
December 9, 2024

It's unstable even in Windows.
So I always get my breath together before I use the remove tool and press Ctrl+S to save it for now, and I use the tool.
I do this every time I paint a stroke, because if I don't, all the work can fly away. (Be sure to save before using the Remove tool)
Some versions of Photoshop 2024+2025 are very unstable.

Participant
December 8, 2024

It did the same thing with me after I updated. It happened on both PS 2025 26.1 and beta 26.1.2. Nothing seemed to fix it, including restarting and changing the processing to more stable. I reverted to PS 2025's older version, which is 26.0 (I did it from Creative Cloud), and it fixed the issue. Let me know if you can try this and if it works for you.

 

Visit my travel blogs and enjoy.

Inspiring
December 7, 2024

Yep, me too.  Udpated to 26.1 and immediatly it started crashing with remove tool, losing all work up to that point.   Reverted back to 26 and problem went away completely.  Using apple M1 Max. 

2Charlie
Inspiring
December 8, 2024

Nice! I'll have to give that a try. Thank you!

SnappyLeeds
Participant
December 2, 2024

I'm having the same issue with the remove tool with larger files. 

2Charlie
Inspiring
December 2, 2024

Yes, smaller files seems to have less crashes. My file is quite big and it crahses quite a lot.

Known Participant
December 1, 2024

I run Mac OSX Sequoia 15.1.1 and Photoshop 26.1.0.

 

Photoshop randomly (and relatively frequently) crashes when I use the remove tool. Not all the time, sometimes I manage to edit a few photos, other times it crashes earlier.

 

Has anyone else experienced the same problem?

Known Participant
December 2, 2024

I pasted part of the crash report into ChatGTP:

This crash report indicates that Adobe Photoshop 2025 crashed on a Mac running macOS 15.1.1 due to a segmentation fault (SIGSEGV), with the issue originating in com.apple.CoreMLBatchProcessingQueue. The crash occurred in thread 93, involving CoreML (likely machine learning-related processing).

Key Details:

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

  • Indicates an invalid memory access, pointing to 0x00000000000001e0, which is not a valid memory region.
  1. Primary Threads Involved:

    • Main Thread: Function calls suggest typical application runtime operations.
    • Thread 93 (Crashed): Linked to CoreML, possibly triggered by specific Photoshop features like AI-powered filters or processing tasks.
    • Thread 4: An active thread named "HB Kill Signal Processor" hints at a signal handler, which might be monitoring or managing app states.
  2. Termination Reason:

    • Namespace SIGNAL, Code 11 (Segmentation Fault).

 

 

Pasting in the Thread 93 log yielded:

 

This crash log indicates an issue in Adobe Photoshop 2025, specifically within its interaction with CoreML and MetalPerformanceShadersGraph frameworks. The crash occurs during machine learning operations, as CoreML appears to be executing a neural network prediction. Let's break down the key points:

Problem Overview:

  1. Crashed Thread: Dispatch queue: com.apple.CoreMLBatchProcessingQueue.
    This suggests that the issue is related to CoreML's batch processing tasks.

  2. Faulting Modules:

    • MetalPerformanceShadersGraph: Handling tensor data for Metal (Apple's graphics API).
    • CoreML: Evaluating a machine learning model or task.
    • Adobe Photoshop: Likely executing an ML-powered feature like neural filters or content-aware fill.
  3. Key Function Calls:

    • MPSGraphTensorData initWithMPSNDArray: The crash starts when converting tensor data.
    • MLNeuralNetworkEngine: CoreML's engine evaluates the inputs for the ML model.
    • MLDelegateModel predictionFromFeatures: Executes the prediction task.
    • Various Photoshop methods suggest the task might involve GPU-based rendering or AI-driven features.
  4. Possible Causes:

    • Incompatible CoreML model: The model being used may be incompatible with the system's hardware or the Metal framework.
    • Memory issues: Tensor data conversion might be running out of memory.
    • Hardware/GPU issues: The Metal API might be encountering an issue with the GPU's performance or compatibility.
    • Software bug: Likely an issue in Photoshop or its interaction with CoreML.
2Charlie
Inspiring
November 26, 2024

This is the exact behavior I'm having too. I have a M1 Max MacOS 15.1.1.

AlanGilbertson
Community Expert
Community Expert
November 26, 2024

Another user reported this problem with more detail. It looks very much like a bug in the code, because it's creating an illegal memory operation. Here's what Apple's dev support says about this particular error:
"A crash due to a memory access issue occurs when an app uses memory in an unexpected way. Memory access problems have numerous causes, such as dereferencing a pointer to an invalid memory address, writing to read-only memory, or jumping to an instruction at an invalid address. These crashes are most often identified by the EXC_BAD_ACCESS (SIGSEGV) or EXC_BAD_ACCESS (SIGBUS) exceptions in the crash report."


I have alerted the Photoshop team. Unfortunately, until there's a fix, the best advice I can give is to not use the Remove tool.