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. ... View more

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. 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. 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: Crashed Thread: Dispatch queue: com.apple.CoreMLBatchProcessingQueue. This suggests that the issue is related to CoreML's batch processing tasks. 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. 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. 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. ... View more

Also, I have tried the recent beta version also and it keeps crashing. I assume that normal and beta versions have different preference files... ... View more

Maybe I should add that I have Generative AI off, and remove after each stroke. ... View more

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? ... View more

There is one thing that still puzzles me. Why would some photos shot in the same environment show banding while others did not. Does Photoshop do some magic so that the "optimized jpeg" option does not utilise the full colour space always (allowing 8-bit to be enough). Because the banding was very noticable in some jpeg photos with gradients, while other jpegs (also with similar gradients) worked much better. ... View more

@Conrad_C thank you for this reply. I have been struggling with this for a year now. Now it makes sense to me.   What happened was I switched to Rec.2020 with a Photoshop upgrade about a year ago, thinking bigger colour space is better while editing 16-bit, but kept saving my photos as 8-bit jpeg with the colour profile embeded. But like you said 8-bit is not enough to cover the entire colour space.   I just tried exporting directly from 16-bit AdobeRGB to 8-bit jpeg and that looks pretty good, very slight banding and a bit of a change in colour. Also tried exporting from 16-sRGB to 8-bit jpeg and the colours are still closer (but not perfect).   Not sure what the optimal workflow is yet, but at least I understand the process better now. Thank you. ... View more

I found this way to somewhat alleviate the dithering. https://www.youtube.com/watch?v=mmwEJkDwvaI   My default colour profile was Rec 2020, but if I instead convert it to Adobe RGB 8-bit using the "Convert colour profile" optionin edit then save the JPEG with embedded colour profile, then it looks a bit better. Still some colour banding, but not nearly as bad.     ... View more

D Fosse, I use Mac OS X. There does not seem a way to pin the association to normal Photoshop there. ... View more

@Jumpenjax thanks for the suggestions, but my idea is not for the subject to be completely untouched by the blur. I want the centre of the blur to be on the subject. And as it is now it is hard to be precise in the placement. ... View more

How do I unfollow this thread? For some reason I started getting emails when people post here, and I can not see where in the thread I am following. The email has an unsubscribe option, but I dont want to remove all Adobe emails, just this thread. ... View more

I think you are right in that the grayscale profile is a problem, but I am not sure it is the only problem.   Doing blur on a grayscale 16-bit image (banding) and then converting it to RGB (looks fine). If I save a grayscale image in 8-bit jpeg, I see banding there. But if the banding would only be in the "display step" (ie not in the image data itself), then opening the jpeg and saving it as a colour 8-bit image should remove the apparent banding (since we are now bypassing the grayscale profile), but it does not fix the issue.   It can still be the profile, but I think it is deeper than just in the step of how the picture is shown on screen, since the banding gets burned into a jpeg when saving it.   I will be doing more in RGB mode going forward and hoping that Photoshop adresses this in future updates. Really appreciate all the info and discussion. If anyone else has experience with this it would be interesting to hear. ... View more

Fosse, your last reply got me thinking.   If the file data is OK, but the display is wrong, then blurring the 16-bit BW image (has banding), and then switching to RGB colour, should remove the banding in the image -- and it does! Before I had always undone the gaussian blur, switch to RGB, and then do the blur again.   That gave me hope, what if I converted the BW 8-bit jpeg to colour, would the banding disappear -- which it did not. So somehow the banding gets locked into the jpeg image (I use Adobe RGB).   What is the best grayscale profile to use? The Gray Gamma 2.2 gave banding, is there some wider profile? I feel like I am opening Pandora's box with all these different colour profiles... ... View more

Thanks Fosse, this is quite interesting and I am learning things.   I wrote "black and white", but it should be "grayscale" mode.   The profile was defaulted to “Working Gray - Dot gain 20%” for grayscale, I changed it to “Gray Gamma 2.2” (16-bit) and still see the same banding when doing Gaussian blur.   Undid the Gaussian blur, switched to RGB 16-bit, applied the same filter again and got a smooth gradient.   Also repeated it with 32-bit just to make sure it has enough bit-depth, but got the same result -- banding for grayscale, smooth gradient for colour. ... View more

I think you missunderstand me.    16-bit black and white --> problem with banding with iris blur and gaussian blur. 16-bit colour --> no problem with banding.   The images are in 16-bit mode, opened from 14-bit Nikon NEF files. The difference is in "black and white" mode vs colour. ... View more

Hej Fosse,   I use a Macbook Pro M1 laptop, did a quick search and that should be a 10-bit capable display. Also important to note is that if I do the blur when the same image is in 16-bit colour mode, there is no banding visible (so the display should be working).   In both cases the image looks black and white, since there is no colour in the actual image, but for some reason the fact that it processes in black and white seems to add banding. ... View more

Hej Jeff, thanks for the quick reply. Yes the "precise previews for 16-bit document" is checked. The issue also persists if I apply the blur effect to the image and view it outside of preview mode. ... View more

This is not solved. I did the fresh reinstall of Lightroom yesterday and then it worked on OSX. Now this morning I tried to run it again, and this time it failed the same way as befpre. I checked in the Console app to see the logs and I again see "Namespace DYLD, Code 1 Library missing". ... View more

Thanks for the quick update!  ... View more

There was another thread where they mentioned that the reason for the crash was Photoshop not having access to the document folder on the Mac. I have not tried it, but in the System settings you might be able to give Photoshop access to the Documents folder. They said it would be fixed in the next version of Photoshop Beta. ... View more

Do you have a backup you can restore from? I used a backup from an hour earlier, and that worked. ... View more

This is the error message in English that I get: "An unrecoverable problem has occurred photoshop" ... View more

The same thing happened to me. I was sitting editing photos and did the update, so used Time Machine to restore the previous verision. The old Beta version runs, but curiously the Creative Cloud app now thinks I run the updated version. So it seems that it does not look at what is installed, but rather have some internal book keeping. ... View more

Hej, I am now on Photoshop 24.2.0 and there have not been any crashes in a while thankfully. Not sure if it was the Photoshop update, or something else that fixed it. ... View more

There was some small update the other day, still crashing occasionally when pressing X (or clicking the swap colours in the GUI).   Has anyone else had this problem? ... View more

Thank you NB for a very comprehensive reply. I also updated the WACOM tablet driver, and for a while I thought it might have been it, but I just had photoshop crash again.   Hoping for the next release to fix the bug. ... View more