Photoshop CC 2018: Healing and Spot Healing Brush Lag

Thanks Pete,
This fixed one of the brush issues, but lag of graphic resizing of the brush still persists:
https://feedback.photoshop.com/photoshop_family/topics/brush-resizing-lag-in-new-2018-update?topic-r...

Hi Adam,
Thanks for the speedy reply.
Nothing abnormal in memory or CPU resources. I've purged the history, tried many combinations of performance variables in PS settings, the only thing that fixes it is a restart of PS.
I'm not sure what to look for in the console log. No errors are showing up for Adobe or Photoshop

I did try a restart and Disk First Aid, neither have resolved the issue

Technically a restart of OS or Photoshop reset the problem, but it comes back after a short time of working every time.

This is happening to me too, I've called tech support twice, I hope Adobe comes up with a solution quick because it's costing many of us time and money for this insane lag, restarting PS over and over again is a lame option and not realistic. Tech support told me to reset brush settings to default but this is a pain too that doesn't always work. I use a Wacom Cintiq 13 touch tablet but it does the lag even without the tablet.

I'm about to go back to 2017 version because this one should never have been released with these glitches. Next time they should have full time professional retouchers and artist use the products before they release them. It would have been discovered in minutes...

Turn off smoothing and you should be good. Seemed to work for a lot of people now.

turning off smothing doesn't work for ever......after cca 1hour of work is there a lag again :( 

I have this problem too and the tool gets stuck showing black on the subject. Rubbish update period. 

I also have this issue. The tool lags several seconds between clicks. Sometimes it behaves as it I'm Shift-clicking (the healing brush makes straight lines between click points). I've restarted my computer several times since the update, and the only remedy seems to be restarting Photoshop when the symptoms occur. I thought it could be a Wacom driver issue, but it doesn't seem to be the case.

2014 5K 27" iMac
4GHz Intel i7
32GB RAM
AMD Radeon R9 M290X w/ 2048MB of memory
250GB SSD

  

I too experienced the "line point between two spots" almost like holding shift between each click. Rebooting PS cleared it up but saving large 16-bit files takes a while. However, I have also recently worked a long period of time without the issue. 

Don't forget to hit the "me too" so this bug becomes a priority

> Back to the clone tool in the meantime. Hope there is a fix for this. Wouldn't have updated if I had known of the slowdown...>

You're not stuck on 2018. You can reinstall 2017 if you uninstalled it. Personally, I keep the last version back for some time after installing a new version—just in case something comes up that makes my life harder.

I am having the same exact issue. Reseting PS fixes it. But, it ALWAYS crops up again AFTER I run the dust/scratches filter. That seems to set it off for me.

Same thing here. Mine happens immediately. I get the lag and the lines. I tried resetting to "use the legacy algorithm" for healing brush, but that almost made it worse. Beta testing during my workday is a hassle. 

I am  having the same problem which never existed with prior versions.  I have a very high end PC with all SSD drives .... this is crazy.  Editing has become a nightmare.  Please fix this ASAP.  Reboots, resets, turning off GPU card, etc. makes no difference.  Unacceptable.

Don't forget to hit the "me too" so this bug becomes a priority

have the exact same situation on Win10 with Intell 8core, 32gb ram and nvidia 1060 6gb. The bug is in the (Spot) Healing Brush tool, the Patch tool works perfectly like with PS18.

I've had the exact same problem. I cursed at my screen all day and finally tapped out. Uninstalled and back to CC 2017.

me too !

Problem solved with Nov 14, 2017 update

Same here , 2017 was like this inte first release too .
Today’s release seems to have solved it. -
- question is why release it with such a unusable blatant bug ?
Us photographer and retouching houses reply on cloning and healing

Is it not being beta tested by Pro people ?

I take it all back - the solution, whatever it was, did not last -

I feel like I've been sold a great looking car but when I looked under the bonnet it had a wound up elastic band where the engine should be! -

Why are large companies allowed to sell things that do not work as described?

and why must we pay for it? the spot healing is broken, i'd like this month's fee discounted thank you Adobe. I'm lucky I have the luxury this week to take some time away from editing.

A lot of companies I support do this.. if they have a moderate to big screw-up they, before anyone even has time to notice, automatically credit the month for free..... A much appreciated and respectful gesture....

I tested this and it gave the same results as restarting the program... works for a bit then goes downhill

Hi Adam, I did this about an hour ago (Reset Prefs on Quit) and so far so good

Update, still working well after 3+ hours :)

Thanks. So far so good here too.

TRashed preferences and it's gone for now. But so are all of my preferences. Bummer of a solution. 

I'm having the same issue also. Tried everything, several PS performance settings, maintenance routines on my Mac, deleting caches....all of it after a few minutes working, the healing brush starts lagging again. Will this be fixed with a patch or should I go back to previous version.

This isn't the solution guys, its posted further down. Slide the smoothing slider down to 0%

This did not work for me

I always work in 8bit, usually RGB.

I've experienced this problem on images ~10,000 x 7,000 pixels (155 dpi), single layer.

Also experiencing this on smaller 1200x1200 multi-layered TIF files (~8 layers), regardless of the toggle sample all layers being on or not.

I counted just now and it took over 20 seconds to clean up a single "spot" (20 pixel brush) on the 10,000x7000 flat image. The time on the smaller one is 3 seconds.

This really should not matter they are the same type of files as the last few thousand files I was using all year long and before.

My use of PS is very repetitive this app should work no matter what the files and it especially should work at least as well as it did before on the same files - unless it is a downgrade!

But as you asked they are just simple RAW files straight out of a Fujifilm GFX 50s on a round trip from some basic batch processing in Lightroom (so it becomes a PS file when I hit the edit in PS comment in Lightroom of course) - if you think it's down to file size what the hell is going to happen when I want to look at large something out the Hasselblad or even larger such as our large format film scans.

Just make it work as it did before we never had to use specific type or size of file before.

BTW - I just reset preferences on quit and of course now my PS looks bad and I need to spend a whole load more time finding my way around it and putting everything back where I expect it to be!!

Happening on all tested files sizes from normal pro cameras, always 16bit Profoto

Seems to happen to me after I run the dust/scratches filter.

> Seems to happen to me after I run the dust/scratches filter.>

So how long has a retouching session been before this happens, and is it always after the dust&scratches filter? I tried it out on an old scan using D&S to remove just the smallest bits of dust, then spent another 15 minutes rapidly going over the entire image with the Spot Healing brush, and I had one incident where it "connected the dots," which it sometimes does, but other than that, it never lagged at all and I never slowed down. So does it take going through a few images like that to make it become a problem?

For me it has nothing to do with dust and scratch. I haven't noticed a pattern, but it will happen shortly into the first image I start work on after opening the program

8 bit, rgb, 5267x5267, 5 raster layers, 4 smart objects (2 with gaussian blur, 1 with liquify and puppet warp), 1 solid color with vector mask . Small lags 1-2 sec. (but with pretty good computer configuration). Tablet used, wacom.

8bit, psd format, 2 layer, 7300x4900px, RGB image

8 bit 10,000x7,000 pixels RGB, many adjustment layers, smart objects, regular pixel layers.
8 bit 4,500x6,500 pixels RGB no layers, just the background

16bit psd, 4000x3000px, one layer!, RGB, win10 PC

.dng file (from Canon 5D3) opened from Lightroom i.e. no layers. I add a single transparent new layer above to do healing. The first heals are ok for a short while then it just gets very slow as reported by others. Have to close and re launch Ps every few minutes to get the speed back. It used to be as close as possible to real time but now it's worse than Lightroom. Using Wacom on MacOs Sierra

16bit, RGB, 25MPix, mouse.
Lag starting after around 25 clicks (+3000Mb of RAM / working set).
GPU peak to 25% during each lag
CPU peak to 30% during each lag

System:
Adobe Photoshop Version: 19.0 20170929.r.165 2017/09/29: 1138933  x64
Number of Launches: 306
Operating System: Windows 10 64-bit
Version: 10 or greater 10.0.14393.1198
System architecture: Intel CPU Family:6, Model:12, Stepping:3 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, AVX2, HyperThreading
Physical processor count: 4
Logical processor count: 8
Processor speed: 3999 MHz
Built-in memory: 32716 MB
Free memory: 2 MB
Memory available to Photoshop: 29447 MB
Memory used by Photoshop: 60 %
Surface Dial: Enabled.
Alias Layers: Disabled.
Modifier Palette: Enabled.
Highbeam: Disabled.
Image tile size: 1024K
Image cache levels: 4
Font Preview: Medium
TextComposer: Latin
Display: 1
Display Bounds: top=0, left=0, bottom=1440, right=2560
Display: 2
Display Bounds: top=0, left=2560, bottom=1440, right=5120
OpenGL Drawing: Enabled.
OpenGL Allow Old GPUs: Not Detected.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
AIFCoreInitialized=1
AIFOGLInitialized=1
OGLContextCreated=1
NumGLGPUs=1
NumCLGPUs=1
NumNativeGPUs=0
glgpu[0].GLVersion="4.1"
glgpu[0].IsIntegratedGLGPU=0
glgpu[0].GLMemoryMB=6144
glgpu[0].GLName="NVIDIA GeForce GTX 1060 6GB"
glgpu[0].GLVendor="NVIDIA Corporation"
glgpu[0].GLVendorID=4318
glgpu[0].GLDriverVersion="22.21.13.8494"
glgpu[0].GLRectTextureSize=32768
glgpu[0].GLRenderer="GeForce GTX 1060 6GB/PCIe/SSE2"
glgpu[0].GLRendererID=7171
glgpu[0].HasGLNPOTSupport=1
glgpu[0].GLDriver="C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_24ddebfb518b5a55\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_24ddebfb518b5a55\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_24ddebfb518b5a55\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_24ddebfb518b5a55\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_24ddebfb518b5a55\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_24ddebfb518b5a55\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_24ddebfb518b5a55\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_24ddebfb518b5a55\nvldumd.dll"
glgpu[0].GLDriverDate="20170718000000.000000-000"
glgpu[0].CanCompileProgramGLSL=1
glgpu[0].GLFrameBufferOK=1
glgpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.50 NVIDIA"
glgpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[65536]
glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
glgpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
glgpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
glgpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
glgpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
glgpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[4096]
glgpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
glgpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
glgpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
glgpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
glgpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1
clgpu[0].CLPlatformVersion="1.2"
clgpu[0].CLDeviceVersion="1.2 CUDA"
clgpu[0].IsIntegratedCLGPU=0
clgpu[0].CLMemoryMB=6144
clgpu[0].CLName="GeForce GTX 1060 6GB"
clgpu[0].CLVendor="NVIDIA Corporation"
clgpu[0].CLVendorID=4318
clgpu[0].CLDriverVersion="384.94"
clgpu[0].CLBandwidth=1.42807e+11
clgpu[0].CLCompute=1627.64
License Type: Subscription
Serial number: 90970897118203259305
GUIDBucket:
Application folder: C:\Program Files\Adobe\Adobe Photoshop CC 2018\
Temporary file path: C:\Users\rogez\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
  E:\, 5,46T, 585,2G free
  D:\, 188,9G, 47,1G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC 2018\Required\Plug-Ins\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC 2018\Plug-Ins\

8bit and 16bit uncompressed TIF files, color space is Adobe 1998. Files are typically 11,000px X 14000 pixels, created with a Betterlight 8K 4x5 scanback camera. 

Mouse here. I have tried with a tablet and am experiencing the same results (no faster or slower)

Intuos Pro 2015 (tested with multiple Wacom drivers, both current and two years old)

Have tried both, same issue.

doesn't matter, mouse or wacom intuos 3, still the same lag 

no diff