P: Slice Tool very laggy

Exact same issue here. Turning off slices gives smooth operation/scrolling again. Turn on slices and laptop/photoshop grinds to a halt with huge increase in fan/processor activity. Nvidia GTX 1050 here. Previous 2019 version of photoshop was fine.

I also have Acronis True Image and I stopped the "Acronis active protection service".
That really improved the speed on Photoshop CC 2018 with Camera RAW 12. Everything now works as it should be.
However when I tried Photoshop CC 2020, it was still a slow and laggy disaster. Totally unworkable.
I have a "Beast of a machine" can play almost all new games with video settings all maxed out, still a big problem with Photoshop CC 2020.
All supposedly improved performance settings didn't make any difference.
So until Adobe comes out with a good version I will keep using CC 2018.

I am also having this issue, even after the update.  The slice tool is unusable and I needed to go back to PS2019 in order to work efficiently.

I am also experiencing the lag. Both at home and work. Both machines have great specs too.

could it be that you have Acronis True image installed? Then stop the service "acronis active protection service"

Write a comment

Still slow, look no change after update.

Still slow for me - there is a massive difference in speed when slices are turned off (scrolling and zooming is super smooth) to when they are turned on (everything slow and laggy).

After the update the workspace is still very laggy when using hand tool with slices displayed VS slices not displayed.
I just noticed this : before the update, moving the document used 55% GPU (Quadro P2000) with slices shown VS 15-20% without slices. After update, 68% GPU with slices and still 15-20% without.
Here is a video of the problem : https://youtu.be/-amITHY2Rgk

Hi Adam,

I've just updated. It's working a lot better, I'm still finding it's slowing down when I get to around 24 slices, it's usable now but not as fast as 2019.

Thanks 🙂

Can someone who's experiencing the slow Slice tool please update to 21.0.1 (released earlier today) and see if this is still an issue? We should have fixed it, but I'd like confirmation. Thanks!