Skip to main content
Liam Coleman
Known Participant
April 5, 2018

P: Dehaze tool causing lag following update to 1.3

  • April 5, 2018
  • 16 replies
  • 615 views

I really like the direction the new Lightroom CC is going, but after I recently updated to version 1.3, the dehaze tool has started introducing serious lag in the desktop program's operation that was not there previously. Lag is experienced when adjusting the dehaze slider itself or when adjusting any other slider on a photograph that has dehaze applied. I am using a MacBook Pro running High Sierra. Would appreciate this bug being addressed in a future release. Thank you.

This topic has been closed for replies.

16 replies

Kelly Castro
Adobe Employee
Adobe Employee
May 21, 2018
@Liam, Thanks again for bringing this issue to our attention. The bug has been identified and a fix will be included in the next release of Lightroom CC.
Inspiring
April 26, 2018
Any information on this issue?
Inspiring
April 14, 2018
I've only today upgraded from version 6.1 to a subscription based license IN ORDER to get the dehaze slider. Unfortunately, I find the same issue. As soon as I use the dehazer, everything slows. The other sliders get very laggy. I've never experienced any slowness or lagginess before in all the years I've used Lightroom. It's making me wonder if I've made a bad decision in switching to CC Classic.
Liam Coleman
Known Participant
April 11, 2018
Hi again, Rick. I have discovered that heavy and previously absent lag is occurring in much the same way as described above in photos with local edits made with the brush tool. Adjusting any slider is very slow and laggy in any photo that has local edits applied (and also dehaze, as described before). Same computer, LRCC version, and operating system. Could you also look into this? Thanks very much.

Liam
Liam Coleman
Known Participant
April 7, 2018
Thanks so much, Rick!

Liam
Rick Spaulding -
Legend
April 6, 2018
Hi Liam,

Thanks so much for bringing this to our attention. We were able to reproduce it and a bug was created. We will update this post when it is fixed.

Take it easy,

Rick