Skip to main content
Adobe Photoshop Family

291 Messages

 • 

6.4K Points

Wed, Oct 18, 2017 6:30 PM

Solved

Photoshop CC 2018: Healing and Spot Healing Brush Lag

In most recent 2018 update, healing and spot healing brush have become much less responsive, sometimes taking multiple seconds after completion of stroke to affect the image.

Late 2016 Macbook, up to date OS and Software

I've done the regular things like turning off OpenCL and changing other performance options... no change.
GIF framerate is sped up 2x 

 

Responses

3 Messages

 • 

100 Points

3 years ago

Try using the slider on the paint brush panel header and setting smoothing to 0. This seems to be working for me, even though it resets to checked when you relaunch.

41 Messages

 • 

964 Points

3 years ago

Can confirm. Healing brush in 2018 is so super slow I am reinstalling 2017 now. I use healing brush all day long, and in 2018 it's so slow that PS is completely unusable for me. It's not just a little slow, it's super super duper slow. I couldn't get through an 8 hour work day with this. 

154 Messages

 • 

2.6K Points

3 years ago

Hey me too!

Mostly 16bit Sony a7r2 files.
2017 iMac, etc

healing brush is unusable, reverted back to CC 2017
Kind of a big bug to miss, get some real retouchers on the pre-release program!

3 Messages

 • 

82 Points

3 years ago

Well, I thought it was fixed because it worked for a short time after resetting all my beloved preferences but now they are gone too and I can't get the healing brush tool OR the stamp tool to work at all; not even slowly. They just don't work. This is pretty nuts. I use these tools for a living. Does anyone know how to revert back to the previous version of Photoshop CC? I do not believe it is on my computer anymore. (Never mind. I am installing 2017 now from Creative Cloud.)

41 Messages

 • 

964 Points

It's really easy. I did it. Go to the adobe cloud icon at the top of your screen, then under photoshop select "other versions". You can reinstall the old version along side the new one. I'm running both now (well, i'm running the old version, the new one is just sitting there until Adobe fixes this).

154 Messages

 • 

2.6K Points

3 years ago

No one should ever remove the previous version when updating - if you use Photoshop professionally you should know this. It would help if Adobe didn't have the remove checkbox marked automatically.

2K Messages

 • 

35K Points

> t would help if Adobe didn't have the remove checkbox marked automatically.>

What would help even more is if they didn't hide the whole thing under Advanced. Just put all the options out in the open as soon as you click Update or Install.

291 Messages

 • 

6.4K Points

Considering it takes 5 minutes to reinstall, professionals should feel free to uninstall or not at their discretion.

1 Message

 • 

60 Points

3 years ago

Hi everyone,
Just reporting I've got the same problem.

4 Messages

 • 

192 Points

3 years ago

I was having the same experience with the Spot Healing brush On Win10. I tried all the suggestions here minus resetting my preferences, and none of that worked. I jumped back into CC2017 to work on a restoration. After some time I closed CC2017, and went back to CC2018 and the Spot healing brush was working as expected. I double checked to make sure I was on 2018, be switching over to the brush tool and saw the new Smoothing and Symmetry settings. I confirmed I was in 2018. but when I switched bach to the Spot healing Brush the lag had returned.

It appears the something with the smoothing gets switched on when using the brush tool and never turns off when going back to the Spot Healing.

41 Messages

 • 

964 Points

3 years ago

I can now confirm that on two machines, even if you turn smoothing off, eventually it starts lagging again. Eventually it slows down again. So we're pretty much back to 2015.5 until this gets resolved. 

Adobe Administrator

 • 

747 Messages

 • 

16.5K Points

3 years ago

Please try these steps and let us know if this gets spot healing working at a normal speed for you.

***Remember it is necessary to disable smoothing with every launch of Photoshop***

To disable smoothing:
  1. Disable the smoothing feature in your Brush Settings (Image 1).
  2. When spot healing tool is active, drag smoothing to 0% (Image 2).

1.


2. 


Thank you,
Hannah Nicollet

3 Messages

 • 

82 Points

I did that and still not working; not even with lag - just plain not working at all now.

1 Message

 • 

62 Points

Works fine if I don't use the brush first but as soon as I use the brush and go back to spot healing it gets slower and slower. File size is makes no difference.  

1 Message

 • 

62 Points

It solves the lag problem, temporarily, but it adds another issue... when removing the Smoothing as described by Hannah, the Healing Brush tool doesn't work properly. It seems to work just like a Clone Stamp.

I have the basic Creative Cloud plan (LR+PS). How can one revert to the previous version (PS 2017)? These last days have been a nightmare and my retouching work is getting delayed because of this bug.

38 Messages

 • 

652 Points

i love how you MORONS at Adobe really test things hard and proper before releasing.  One of the most used tools in all of photoshop and you dont even test it? lol you guys are a JOKE!!!!!!!

23 Messages

 • 

520 Points

"Disable the smoothing feature in your Brush Settings (Image 1)."

Great... easily done.

"When spot healing tool is active, drag smoothing to 0% (Image 2)."

How on earth do you do this? If the brush properties are open, you are using the BRUSH, and NOT the SPOT HEALING TOOL. If you then tap on the Spot Healing tool, the brush settings are disabled and there is NO SMOOTHING SLIDER in the spot healing brush to "drag to zero" as shown in "Image 2".

Can you please give alternative instructions which do work? Thanks in advance. 

1 Message

 • 

82 Points

3 years ago

Spot healing tool in latest update of Photoshop is totally unusable due to lag. Working on 16 bit, ProPhoto RGB,  over 1 Gb files, on Mac Pro with 64 GB memory, running MacOS 10.12.6. 
Switching back to CC 2017 to meet deadlines.

6 Messages

 • 

190 Points

3 years ago

Same problem, just wasted the whole morning trying to finish a retouching job. Going back to 2017 version. Adobe get your head out of the cloud and fix your software!

38 Messages

 • 

652 Points

they are idiots who release software without even testing it lol.  next they will release software where the brush tool doesnt work because they dont even try brushing before pushing a new release out.  The people who make the software obviously dont use it

Champion

 • 

1.6K Messages

 • 

28.4K Points

The bug is present only for a small number of users. Myself and all the retouchers i know aren't seeing the issue.

Stop being such a drama queen and just use CC2017 until they fix.

291 Messages

 • 

6.4K Points

Eartho, +1 for no drama please...
But 82 voluntary reports is not a small number for a bug (go look at past bug reports), it's reasonable to expect adobe to have caught this one. But they didn't, they're human, so hopefully they can figure it out soon.
Paying monthly for a service comes with certain expectations, one of which is with a dedicated steady stream of income, innovation and reliability should be expected.

38 Messages

 • 

652 Points

eartho im not being a drama queen.  I am fed up with lightroom classic and now this.  it is beyond a joke.  I am tired.

38 Messages

 • 

652 Points

Stephen yep finally someone agrees :P 

2K Messages

 • 

35K Points

> Paying monthly for a service comes with certain expectations, one of which is with a dedicated steady stream of income, innovation and reliability should be expected.>

I'm pretty sure we can say that about any software we use. In this instance, unfortunately no one tested the workflow that gives rise to the problem. The individual tools work just fine, but in combination go haywire. Or perhaps there may be more than one issue, depending upon OS and computer and. . . It's unfortunate, and something no one, least of all Adobe engineers, want to have happen. They're not the company and they don't make a living no matter what they do to the customers — and actually, neither does Adobe, and the management knows that.

At least Adobe, perhaps with the historical knowledge that these types of issues do arise, made it very easy to re-install if you were an early adopter and/or you fell for the very bad design of the CC app that uninstalls your previous versions by default.

But tell me how many people don't depend upon the OS they run? Windows forced an upgrade that left people unable to use the software they needed, tried to root out 3rd party software that blocked Windows constant effort to force the update, and their latest version just came with big warnings about the BSOD that they might well get if they updated.

Apple doesn't let you get earlier versions of their OS if you want to install not the latest, but the next to latest, for instance, and you haven't already installed it on at least one machine. Updates get released with warnings about Mail becoming unusable all the time for the past several versions of the OS, and that's just the tip of the iceberg.

I update with trepidation no matter what the software I'm updating because a few decades of this, I know it's always perilous. My hardware, my OS, my installed apps, my workflow is different enough, I can have a problem where 9/10ths of the rest don't even notice. I've been months late to the party just because I've been in a project with a deadline where I couldn't risk updating, so regardless of a lack of uproar over the update (when does that ever happen?), I held off.

But with Adobe, one doesn't have to. They've made it so the versions are sandboxed well enough, they run concurrently. You can have the latest and the one before that and the one before that, all installed. Maybe that leads to them rushing features out the door a little too quickly because you can always use an earlier version. I honestly have no clue about that. But they do provide you with a cushion.

Getting mad at them because it's subscription software is another matter. Paying monthly has nothing to do with it.  If I have a bug in my workflow with software that has a perpetual license, I've paid, I don't get my money back, and I can wait just as long if not longer for it to be fixed. It's simply a separate issue from there being any bugs at all, regardless of how serious. It plays a part in innovation, obviously, though for better or for worse depends upon how you view it, but it has no perceivable role in bugs getting into the world. If that were the case, then the opposite, Apple's OS which is free, ought to be bug-free, no? They have no monetary incentive to push it out to us too untested, do they?

1 Message

 • 

84 Points

3 years ago

I'm done with finding ways to fix it, just uninstalled it and reinstalled CC2017, back to normal now, feel so fast after few days of struggle...Happy!

38 Messages

 • 

652 Points

Yep, for this AND lightroom i went back to the old versions after their claims that lightroom was better too lol

1 Message

 • 

70 Points

3 years ago

Likewise, went back to PS 2017 and can now work in a normal fashion. 

Adobe Administrator

 • 

747 Messages

 • 

16.5K Points

3 years ago

Hey Everyone,

Thank you for the feedback - it has been very helpful. We're working on an update to address this issue in the near future.

I understand some haven't had success with the workaround and wish to go back to the previous version. The concern I have heard from a few is that their previous version of Photoshop has been deleted. That shouldn't be a problem. Launch the Creative Cloud and beside Photoshop choose the drop down menu and select "Other Versions" to install a previous version.*


Thank you for your patience.


Hannah Nicollet

* For full instructions go to https://helpx.adobe.com/in/creative-cloud/help/download-install-app.html and scroll down to "Install previous versions of apps"

38 Messages

 • 

652 Points

Hey Hannah, how bout you now put your attention to going and fixing Lightroom Classic which you broke and made 4 times slower than 2015.12

Champion

 • 

1.6K Messages

 • 

28.4K Points

Michael, this isn't a LR thread and i'm thinking that Hannah probably wasn't responsible for "breaking" LR. If you're having so many issues with that app which others aren't, perhaps the problem is on your end?

10 Messages

 • 

268 Points

While I don't share your experience with the new Lr classic I have been repeatedly disappointed with several CC updates pushed to the public, because of the more expedited time line Adobe has put it's self into. This promise for faster updates is causing to be unstable, because of the limited amount of testing. Lr classic however, has plenty of time to have been made ready for the public, so I sympathize.

With that being said please don't hijack this thread. Start a new one dealing with your specific issue, so that it can be deleted with constructively.

41 Messages

 • 

964 Points

Thanks Hannah for doing a thankless job. 

13 Messages

 • 

208 Points

3 years ago

I'm in the same boat as everybody else here. I rely on this application to keep my business running. This issue has caused me a good degree of anger and productivity loss over the last few days...... As a gesture of good will from Adobe, to it's Photoshop users (just to show you care), some sort of recompense on the subscription or such like, would not go astray. I cannot believe this new version could have been released with such a basic and fundamental flaw in a tool that most retouchers use daily.

13 Messages

 • 

208 Points

With OnOne pushing their increasingly competitive product hard at the moment, it won't take much of this sort of rubbish for customers to move on, and try different software to get the job done.

154 Messages

 • 

2.6K Points

As it's been said earlier, if you use PS I any professional capacity you should know not to jump in on important work. Install along side a version that works well and test when you have time. I installed CC 2018 and after 5 minutes of slow healing brush I checked the feedback site, saw it was an issue with the update and went back to CC 2017. No productivity lost.