Skip to main content
T
ttnewton
Participating Frequently
January 30, 2023
Question

Develop mode slows to a crawl on a particular photo, CPU usage skyrockets.

  • January 30, 2023
  • 6 replies
  • 2960 views

When I try to edit a particular photo (but not other photos) using the Develop mode in LRCC v12.1 (the most current version as of now) my computer grinds away, but is unable to accomplish any edit function except glacially with occasional blips of apparent activity. Meanwhile CPU usage soars for the app. If I switch to Library mode, CPU usage reverts to normal and LR again becomes responsive (but of course I can't edit the photo in that mode). Allowing the app to run in Develop mode overnight (as if it might need some time to clear out background tasks) does not improve the situation. If I try to re-crop the photo, for example, it could take ~5 minutes for LR to move an edge slightly.

 

I reverted to the previous version LRCC v12.01, and can once again edit the same photo normally. I'm using a PC on Win10.

If someone at Adobe wants to test for this behavior using my photo file, let me know and I'll upload it for you.

 

This topic has been closed for replies.

6 replies

GoldingD
GoldingD
Legend
February 2, 2023

From your System Info

DirectX: NVIDIA GeForce GT 1030 (31.0.15.1694)

so GPU driver v516.94

see:

https://www.club386.com/nvidia-geforce-528-24-whql-drivers-iron-out-issues-with-a-bunch-of-adobe-apps/

mind you, that has not helped John

    T
    ttnewtonAuthor
    Participating Frequently
    February 5, 2023

    GoldingD, your observation was very helpful! Thank you! I hadn't realized NVIDIA recently updated my driver.
    So with the updated NVIDIA driver, LR Classic v12.01 works better than ever. It's the most usable LR has been on my PC in a long time. But still, LR Classic v12.1 experiences long delays & fits on that one photo (that I've identified so far), though they are not as interminable as before the NVIDIA update. 

    Upshot is, I still have to stick with v12.01 to be able to edit that photo (and perhaps others I haven't yet discovered) but v12.01 is working great now. So there's that!

    Thanks again for your observation!

    GoldingD
    GoldingD
    Legend
    February 1, 2023

    Try your problematic photo with the Use GPU option off. 

    Yes, I know, not desired, And, sorry if I overlooked a previous reply.

     

    Might be an issue with that specific GPU, Might be an issue with that GPU driver, that GPU driver issue might not be fixed via update. Might be a LrC problem with that GPU.

     

     

      T
      ttnewtonAuthor
      Participating Frequently
      February 5, 2023

      Thank you GoldingD! I tried with the GPU off per your suggestion. (Great idea, btw!) Results are that on that one photo LR Classic v12.01 becomes useable but only barely, while LR Classic v12.1 is simply unuseable. 

      Thank you for the suggestion!

      J
      johnm59973136
      Known Participant
      February 1, 2023

      see my similar case: Re: Dehaze in LR Classic 12.1 has severe performan... - Adobe Support Community - 13536145

       

        T
        ttnewtonAuthor
        Participating Frequently
        February 2, 2023

        Interesting, John! Looks like I have the same GPU as yours, and similar behavior!

        T
        ttnewtonAuthor
        Participating Frequently
        February 1, 2023

        This problem persists and is reproducible across multiple re-installs on my PC with the latest LRCC Classic build (v12.1), but does not occur with the immediately prior build (v12.01). Clearly, something is broken with the latest build (can I be expected to conclude otherwise, at this point?) I've tried every potential remedy that has been suggested here, plus everything I can think of on my own. I will not be able to continue with future LR upgrades if no resolution to this reproducible problem surfaces, but I will need to keep paying monthly subscription for using v12.01 from now on. This prosepct seems unfair to me, but is apparently what I'm looking at. Thanks for your attempts to help so far. Any further thoughts, especially from any Adobe reps?

        C.Cella
        C.Cella
        Inspiring
        February 1, 2023

        @ttnewton 

         

        In LrC go to "System Info"

        You will be given the cahnxe to save the info as a text file.

         

        Save it and share it here.

         

        @Rikk Flohr: Photography and the Adobe LrC team can most likely investigate further and test, with your DNG,  on a machine with identical or at least similar specs to yours.

         

        It is not the first time that a new version of LrC  has issues that before were not present.

         

        .

         

         

          T
          ttnewtonAuthor
          Participating Frequently
          February 2, 2023

          C.Cella, thank you! I did this and shared it in a reply to Rikk, above! 🙂 

          TheDigitalDog
          TheDigitalDog
          Inspiring
          January 30, 2023

          If this only happens with one document, yes, you should save it as a DNG (so all your edits are enclosed with the raw) and upload it to something like Dropbox so we can examine it. 

          Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
          T
          ttnewtonAuthor
          Participating Frequently
          January 30, 2023

          Please see my above reply to Rikk Flohr.

          Rikk Flohr_Photography
          Community Manager
          Rikk Flohr_PhotographyCommunity Manager
          January 30, 2023

          I would be happy to look at the file if you can upload it. 

          Rikk Flohr: Adobe Photography Org
          T
          ttnewtonAuthor
          Participating Frequently
          January 30, 2023

          I exported the file as a DNG and attempted to upload it here, but get the following website error, and cannot upload it.

          Correct the highlighted errors and try again.

          • The attachment's developgrindstoahalt_on_my_win10pc_in_lrcc_classic_v12pt1_(2015_10_14_095211).dng content type (image/AdobeRawDNG) does not match its file extension and has been removed.
          T
          ttnewtonAuthor
          Participating Frequently
          January 30, 2023

          Ok. Here is the link on my Google Drive...

          https://drive.google.com/file/d/1w9NfSS9ltTuRbVBNQ_0Klr4ApKU0H-k7/view?usp=sharing


          Note that when I view the file from that link on my PC (via the windows dng viewer plug-in?) I do not see the edits I have made to the file, but rather the original raw file. I expected all my edits to be attached to the DNG since I prescribe that LR produces XMP side-car files by default. I don't know if the reported problem will exhibit on the unedited raw file. Let me know if there is some additional measure I need to take so that you can get the edited file.

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices