Skip to main content
Damon D Bell
Known Participant
September 29, 2020

P: Liquify Tool Crashes with Assertion Failed! error on all Windows systems

  • September 29, 2020
  • 51 replies
  • 13243 views

If the Liquify Tool is used between 475-500 times within the same Photoshop CC 2020 session it gives an Assertion Failed! error and crashes Photoshop.  This is very repeatable and happens on every Windows system in my testing.  I originally reported this back in version 21.2.2.  It is still happening in version 21.2.4.  I never received any reply to the prior post so not sure if anyone from Adobe saw it.

It is easy to recreate this.  Just running a 1 step action with Liquify in a batch process will always crash Photoshop with this error from 475-500 images. This only happens in CC 2020 but not CC 2019.


Image is not available

 

 

This topic has been closed for replies.

51 replies

Damon D Bell
Known Participant
March 7, 2023

@Mohit Goyal 
@Dramenon 
@J453 

This issue is back again in the latets Photoshop 24.2.0 release on Window 10 and Windows 11.  Same as last time, Mac is not affected.

Since 24.2.0 was released, I've had a bunch of Windows users reporting crashing. I've been able to repeat this on my windows machines and it is very repeatable.

In my testing, to remove my plugins from the equation, I jsut wrote a 1 step Photoshop action to apply a face aware liquify to the image. Then, batch processing the action through the Photoshop Image Processor script, it wil produce the crash.  I've tested this on 24.2.0 and the 24.3.0 beta with the same results. The only difference is that before it was giving the assertion failed error message. This time it just gives the crash report dialog.  Other than that, everythig else is the same and it seems to happen between 400-500 images ran through liquify within a single Photoshop session. 

This doesn't happen on 24.1.1. It started on 24.2.0. I;ve verified on my computer as well quite a few of my plugin users' computers that it just started (again) on 24.2.0.

I am a plugin developer and 3 of my plugins utilize Face Aware Liquify as part of a sequence to determine face position. The plugins then use the face position to auto compose the images.  These 3 plugins are used heavily in volume batch processing my hundreds of professional photographers in the school and youth sports photography industry. So this is a major issue disprupting their volume workflow. It's not a minor issue for them. 

This is the 3rd gtime this issue has popped up. i reported this in CC 2021 and then it was fixed. It came back in CC 2022 and was fixed again. Now it has popped back up in CC 2023.  Can you please take a look at this and see about getting it fixed again? please respond and let me know because this is a major issue for my customers as well as myself because my plugins are dead in the water for Windows right now because of this issue. So this is having a major affect on my business too.

Thanks

Participant
May 26, 2022

liquify tool is currently broken. It hasn't been fixed.

Participant
May 25, 2022

Hi,

 

I have updated to version 23.3.2 but still the Liquify tool crashes. It allows me to use the tool but it crashes every time I click OK to accept the changes I have made. And theb I have no other option than do ctrl + alt + delete and quit shut down PS. It really frustrates me not to be able to use the tool.

 

Best regards,

Tuisku

Mohit Goyal
Community Manager
Community Manager
February 17, 2022

Hi all,  

 

We're happy to announce the release of Photoshop 23.2. This update includes the fix for this issue. To see the list of all fixed issues, click here

 

To update Photoshop to 23.2, click "Update" in the Creative Cloud desktop app next to Photoshop. More detailed instructions for updating  

 

Let us know if the update resolves the problem for those affected and share your feedback with us.  

 

Thanks,

Mohit

Damon D Bell
Known Participant
February 4, 2022

@Dramenon 
I just downloaded and tested the latets beta pre-release version and this appears to be fixed.  So thank you for that 🙂

Do you have an approximation for when the fix will be in the public release?

Damon D Bell
Known Participant
January 20, 2022

@Dramenon 
Awesome, thank you 🙂 I am heading out of town on Sunday and won't be back until 2/2. I will only have a Macbook M1 with me. So I can't test on my own Windows machine until I get back on 2/2 (unless it is in a pre-release tomorrow).

However, I will be with a bunch of Photographers at a trade show who are running Windows Photoshop. If it is in the regular beta release then I'm sure I can some of them to install the beta release and test. I'm not sure if bugs fixes are the same for the regular beta vs the pre-release beta.  If not, then I will test first thing when I get back in town on 2/2 unless it is releases in tomorrows pre-release.

Dramenon
Community Manager
Community Manager
January 20, 2022

I have verified the fix and we are working on getting it thru the pipeline and testing other configurations.

Hoping to get this out soon. 

/end of line/
Damon D Bell
Known Participant
January 19, 2022

@Dramenon 
Thank you very much for the update.  I will test it when it is ready.  Also, will the fix be in the public beta release too?  If so, then I can have some of my plugin users test it as well when it is released.

Dramenon
Community Manager
Community Manager
January 19, 2022

We are working on the fix.

@Damon D Bell since you are on PreRelease you may get a chance to put it thru it's paces as well before it goes public. Watch for an email as I will update the ticket you filed when it is ready to test

/end of line/
Damon D Bell
Known Participant
January 18, 2022

@Dramenon 
Were you able to reproduce this in house?  There have been a lot of users of my automation plugins reporting this to me. So I know it is pretty widespread. My automation plugins use the liquify tool during the batch processing. The issue itself isn't related to the plugins. I can recreate it without the plugins. However, the plugins are affected by it because they are using the liquify tool.

Any update would be appreciated.  I am having to answer about this right now to a lot of plugin users who are reporting it. I just want to know what to tell them.

Thanks 🙂