Skip to main content
Participating Frequently
June 9, 2010
Question

Lightroom 3 Freezes On Dust Spot Removal

  • June 9, 2010
  • 33 replies
  • 41753 views

I am going through a 300 old photos that were scanned to .jpg files and cropping/adjusting the photos to create a DVD slide show.  When I first started, Lightroom locked up a couple times using the dust spot removal tool.  The cursor was a closed hand and nothing responded.  After killing the app a couple of times, It was working for about a hour, and then started having problems again.  When I clicked on the spot removal tool, the cursor stayed as a closed hand.  I quit and came back it. The spot removal again locked up the application.  It seems to happen on larger spot removals.  Trying to modify the large spot removals also causes Lightroom to hang up (last time was with a resize cursor). 

I am running the 64 bit version on Windows 7 Professional, 6GB Ram, Quad-Core, no other programs running.  My 300 photos and catalog (with ony these photos in it) are on on an Solid State Drive.  I am using duel monitors with duel ATI Radeon HD 4600 1GB cards.

Message was edited by: thaehn

    This topic has been closed for replies.

    33 replies

    Participating Frequently
    July 12, 2010

    I am upgrading my memory soon (2 GB to 4 GB) so hopefully that helps! 

    web-weaver
    Inspiring
    July 13, 2010

    It will help some. But according to my observations it's more a question of CPU power and speed. Unfortunately you can't upgrade that.

    web-weaver
    Inspiring
    July 12, 2010

    This in advance: I'm running WIN XP SP4 with all available patches; have 4 GB of RAM; have a dual-core processor at 3 GB.

    Apart from my drive C, I have two internal hard drives in Raid 0 configuration (thus they show up as one drive). I also have an external hard drive that's in Raid 1 ( "mirroring') and is connecte by fire-wire 400.

    Yes LR "freezes" when using the dust spot tool and also when using the adjustment brush or - but to a lesser degree - when using the grad filter.

    My observation though is that it's not a true "freezing", because if I wait long enough LR starts working again. So when using these tools, LR gets extremely busy und just doesn't have enough resources left to respond to further commands right away - but it "stores" the comands and acts on them eventually.

    If I turn on my task manager I observe the following when using these tools: the CPU gets extremely busy (i.e. the green bar is at 100%)  while the RAM usage is high but not to the max. The "freezes" occur when and as long the CPU works at 100%. If the CPU is below 100% LR responds sluggish and the response is normal again when eventually the CPU usage is at 0%.

    Also, in my observation, this behaviour of LR is compounding, i.e. the wait-times for my CPU to get back to 0 are increasing, the longer I work with these tools or the more photos I work on. Re-starting LR does not bring change: the behaviour establishes itself when using the tools again. It is as if LR needs to do some work in the background and that this background work piles up the longer I work in LR.

    I am not a software or hardware specialist, so the following observations are somewhat subjective and not really quantifiable.

    In Photoshop I observed a similar behaviour (although never as bad) when working on files of 500 MB and above. It was particularly bad when working on photos residing on my external RAID 1 hard drive. I had a hunch that it might have to do with the reading and writing from a drive that a)  is external and b)  is  in RAID 1. It is known that RAID 1 has slower writing (and also reading) speeds than RAID 0 (or no RAID at all). So in Photoshop I managed to cut down on the unresponsiveness by moving large files to my internal RAID 0 hard drive and working from there.

    From this experience I come to the assumption that some of the "busy-ness" in LR (or of the CPU) is due to reading/writing to/from the hard drive.

    To test this assumption for LR, I moved some photos from my external (RAID 1) to my internal (RAID 0) hard drive and did some "intensive" work: first some "fancy" lens correction, then a few grad filters, and a "final touch" with the adjustment brush. I thought that LR could handle these tasks somewhat better when the photos were on the internal drive - so some of the "sluggishness" or " freezing" is due to the reading/writing from/to the hard drive.

    Acually I cannot explain why this should be so: In my naivete I thought LR writes everything only into the catalog (?), that - by the way - is on my internal RAID 0 drive.

    I think it would be good if Adobe could look into this and maybe give us some recommendations, just as they do for Photoshop by saying that the scratch disk should be on a different drive than Photoshop.

    But it seems also that local adjustments - spotting, adj. brush. etc - are a very high "number-crunching" business for LR - independent of where the photo is located on the drive. (Interestingly the grad filter is not as bad as the adjustment brush). The clone-tool in Photoshop hardly registers on my CPU and if at all only with a very short spike, while the clone tool in LR sends the CPU through the roof for 10 to 30 seconds- even when the photo in question is on the internal drive.

    I'm sure loots of people will now tell me that this is due to the difference between pixel-based adjustment and non-pixel-based ones. OK, I acknowledge that. But still ...

    It seems some guys are still in denial about this (or maybe they have two quad processors and 16 GB of RAM):

    But it's a fact: LR has a hard time with localized adjustments. There must be by now 100's of complaints to that respect, and that can't be dismissed by blaming it on the hardware specs alone.

    I just hope Adobe is working on that.

    LR3 is a fantastic program that I would not want to work without. Often I have to work on a lot of photos with a very tight deadline. Without LR it would be impossible.

    Thank you,

    ErnstK

    Participating Frequently
    July 12, 2010

    Thank you for your response. I took Lr3 to my officice which has a 64 bit platform computer and spot removal brush worked spontaneously.

    --

    Barry Liebowitz, M.D.

    President, Doctors Council

    http://www.doctorscouncil.com

    web-weaver
    Inspiring
    July 12, 2010

    Glad, you've got it working.

    May I ask what your processor and RAM is at your work computer?

    ErnstK

    Participating Frequently
    July 12, 2010

    Just purchased Lightroom 3, the dust spot removal simply does NOT work. Spending the 299 and finding this basic fault is a great disappointment and after 12 hours of trying everything I am going to return this new release. This is not Beta this is a supposed finished product.

    Participating Frequently
    June 24, 2010

    Oh yeah -- it doesn't matter whether I've used the Adjustment Brush before. It's just as slow with images that have no previous Develop adjustments at all.

    Participating Frequently
    June 24, 2010

    This problem isn't limited to Windows -- I'm experiencing it on my MacBook Pro. This is an old model -- 1.83 GHz Intel Core Duo, with 2 gigs RAM. But I tried Spot Removal with the LR3 Beta 2 --- it still works until the end of the month --- and it works fine, despite my pokey machine. Yet with the final version of LR3 Spot Removal is excruciatingly slow. Click on a spot and it takes a good three or four seconds for it to choose the spot it wants to clone or heal from, and in the meantime my mouse is frozen. It's even worse when I try to move the spot it's cloning/healing from -- that takes about 15 to 20 seconds to render.

    So something changed between the beta and final version, and not for the better. Whatever it is I hope they fix it soon.

    Participating Frequently
    June 24, 2010

    I hope this gets fixed soon as well.  I got the latest drivers installed for my nvidia card, changed the settings as suggested in another thread, but it has not helped.  I returned to an image I was having difficultly with before (froze LR) and tried to add a few new spots--that worked fine (albeit slow) but when I tried to move a spot slightly (and this spot had been problematic before) LR froze again...bummer.  FYI, it's a RAW file I'm working with.

    Participant
    June 22, 2010

    I think this is the same problem, and a little bit more info there; http://forums.adobe.com/thread/660718?tstart=150

    Participating Frequently
    June 22, 2010

    Jeffry,

    Thanks for responding. Obviously none of the messages in the thread have any solution. It seems to be a problem with Lightroom 3. I can't believe Adobe would release a program this sophisticated with this kind of flaw. I can only hope that upgrade 3.1 is coming quickly.

    George

    Participant
    June 23, 2010

    Yes it's a real pain!!! Any idea how long it usually

    takes for the next release to fix this? Im tempted to go back to LR2.7 for now, but expect this to be quite alot of work!

    Participating Frequently
    June 21, 2010

    I was going through the same frustrations until I found this thread.  Reading through the posts made me think that working on JPEG files might be the  problem.  I rebooted Lightroom and opened a RAW file and the dust spot removal worked just fine. Then I tried it on another JPEG and it froze again. That's not enough for a scientific judgement, but it does seem to help. Saving in TIFF files might help as well. 

    Is anybody at Adobe listening?

    Participating Frequently
    July 16, 2010

    I also have the same spot removal problem.  However, mine is extremely bad with TIFF's, however, after a number of spot removals or local adjustments in RAW (Sony ARW - Alpha A700) it also slows to a crawl.  Also most local adjustments also slow down dramatically with TIFFS.  25 - 30 mb in siz.  The spot removal is so bad that even the slight touch of the mouse and the file reloads.  It is so frustrating and painfully slow - often 10 - 20 seconds between mouse movements.

    I have this same problem on both my main system and also on my notebook.  LR 2.6 was fabulous and I was in a hurry to get the lens corrections in LR3 - huge mistake!!!

    Main system - Windows 7 64 bit pro, intel dual core 2 quad, 2.66ghz, 8 gb ram, WD velociraptor 300 gb drives

    Notebook - Asus - windows 7 64 bit pro, core 2 quad, 2.6 ghz 4 gb ram, 320 gb hd

    I had a similar problem but only with the main system when using LR 3 beta.  I reported it and the respnse was "thankyou" we will look into it.  Well obviously they either didn't look into it or were in to much of a hurry to get the final release out the door.

    It is so bad that I have to my long term back ups and reinstalled 2.6 and the 2.6 cataloques and am importing the new raws into 2.6 - painful.

    Bob

    Participating Frequently
    June 18, 2010

    Reading your post again, I notice you use dual ATI cards. This FAQ from Adobe (http://kb2.adobe.com/cps/404/kb404898.html), concerns problems with Photoshop (CS4&5). One "fix" is to remove one of your video cards. I have no idea if this will cure your problems, but you might give it a shot.

    Graham

    Participating Frequently
    June 18, 2010

    I'll add (since you are talking about it) that I did not do any lens/perspective correction on the photos where LR froze.  Also, I updated my video card drivers yesterday and there was no major difference...still very slow and I just basically didn't push it to avoid the program freezing on me again.  I'll try doing the spot removal brush edits first, but honestly that is kind of annoying because one of the great things about LR is not having to do edits in a special order.  I hope someone gets this fixed!!!

    June 18, 2010

    ditto.

    Thinking Vista x64 was the problem, as people are always bagging me that I've still got it, I went and upgraded to Windows 7 Ultimate.

    Same thing happens.  If Lens Correction - Manual Transform is active (ie sliders not zero), then Spot Removal gets very very very slow.

    It can't be the machine I'm using - everything else on it now runs like the wind.  I'm going to keep plugging on and trying out different options, next is a disk defrag to see if that helps, but this must surely be a bug, and if it only affects certain users (not everyone) then there must be some tool Adobe can provide that can take the donkey work out of checking my computer's config is correct and eliminate the "Well It Works For Me.. blah blah" from the conversation.

    ? dunno really where to go next except to leave a message here and see if someone can help.

    Peter

    Participant
    June 18, 2010

    i have the trouble with spotting. after 10-20 spots gets slower and slower with beachball spinning for more than a minute.

    iMac i7( 8 processors),8GB,10.6.3, LR3