Participating Frequently

Question

Lightroom 3 Freezes On Dust Spot Removal

Forum|Forum|15 years ago
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.

Show previous replies

D

Daniel Perlak

Participating Frequently

Lighroom 3.4 RC still has this issue. I have noticed it on Windows XP 32-bit then on 7 when I upgraded the PC. Also on my mobile workstation which was on Vista 64-bit and has also been upgraded to Windows 7.

It is only a problem with non-RAW files such as JPEG, TIF(F) or PSD. This has caused me huge irritation as I expected handling RAW files to be more intensive.

I have noticed that Lightroom seems to re-load non-RAW images often. Loading will appear at the bottom centre of the image while working on it every 5-20 seconds which slows eveything down. No problems at all occur with RAW files with 1:1 previews rendered.

DanTull

Adobe Employee

I have noticed that Lightroom seems to re-load non-RAW images often. Loading will appear at the bottom centre of the image while working on it every 5-20 seconds which slows eveything down. No problems at all occur with RAW files with 1:1 previews rendered.

Hmm. By any chance do you have auto-write to XMP enabled? The only reason that comes to mind that LR might re-load non-RAW formats but not RAW formats is that the timestamp is changing due to metadata having been written to them (due to the changes made in Develop).

DT

JW Stephenson

Inspiring

Dan,

Just to confirm, the clone/healing tool is still problematic in 3.4 RC (sluggish at times, causing "Not Responding" window at times) when many spots are utilized. The problem was introduced with v3 and is most noticeable on non-RAW files (the only non-RAW I generally work with is JPEG scans). The real killer is to accidently adjust the size of an existing spot when you thought you were adding a new one - major hang-up (although give time, it does recover).

I filed a bug report with the first v3 beta and have been in contact with Adobe, providing files, information, etc. in the past but have not heard back from that email thread in quite some time. Hope it stays on the list of things to fix.

Jeff

M

makebbekus

Participant

I'm running Lighroom 3.2 on Mac OSX with an i7 and 4gigs of ram and am also experiencing the problem. Adobe, please fix this!

B

brad_judy

Participant

I'm having the same issue of hanging on the spot tool. Sometimes it just hangs for a few seconds and other times it stays hung and needs to be closed using the task manager. At the moment, it's hanging on a 16-bit grayscale JPG. I have noticed that it seems to hang more on larger spot sizes (75 or larger).

I'm running LR 3.2 on Windows 7 64-bit with an i7 CPU, 8GB RAM, ATI 5770 video card (just updated the drivers, which didn't affect the spot problem).

It's a pretty frustrating problem and I was hoping that 3.2 would bring a fix, but it has not.

G

George in Fair Oaks

Participating Frequently

I'm sorry to hear that upgrading to LR 3.2 didn't solve your problem. I've had no difficulties with the spot tool since I upgraded. What I do find is the LR 3, or 3.2, is still much slower than 2.7. I don't know what that's about but from what I read it is a systemic problem and not related to processors, memory, or whatever. It may be that you just have to wait it out on larger spots. The ongoing problems with LR3 are very frustrating. I hope that Adobe is still listening and that 3.3 will address some of the speed issues.

George

W

wintoid67

Participant

Same issue here on Windows 7 64-bit. I have found that the freeze frees up if I hit the Windows key. Anyone else?

R

rjh1007

Participating Frequently

How I wished it worked. It appeared to work using the clone/heal tool then immediately froze up completely the second time I tried it. The same for any movement of the mouse on any TIFF file - it either re loads or freezes up for 10 - 20 seconds.

Adobe has gone from a well functioning LR2.7 to a totally unusable tool in LR3. I can't even switch between installs on a different system as it freezes up on the second system as well.

I have reinstalled DXO and Bibble 5 - they work fine albeit in a less elegant manner. I have also gone back to LR 2.7 for my critical work. I should have known better than to upgrade on the first release.

I really hope that Adobe is reading the forum comments and takes seriously some of the serious issues that have crippled many users workflow with LR3.

A

Anonymous

on a lighter note.. i wonder if the credits page is going to change much when LR 3.1 finally gets pushed out??

---

yes I realise that was a bit of a snide comment, but I'm past the point of thinking these forum pages are anything else than a way for us to vent our anger at being duped, without actually being heard by anyone. if I hadn't relied on LR for so long I wouldn't be this peeved, i would have just switched to Bibble or PW4 or Corel PSPx2, but LR is ease of use, and when they've had their problems in the past, then overcome them, that gave me confidence that this version 3 would be an extension, and not a backwards step.

The new Noise Reduction WROCKS! Going back to LR 2.7 is not a possibility for me, as I have come to rely on the new noise reduction in LR 3. I really thought all these things got fixed in the past - back in 2008 with LR2.3 or whatever it was that fixed the major time lag in adjustment brush back then.

They fixed it before.. and they shall fix it again... I just wish they'd hurry up about it! (I won't go on and on about the fact they broke it in v3 after they fixed it sometime in v2 .. that would be chirlish, wouldn't it)

So.. the two things that made me upgrade to LR3 were (1) lens profiles,.. which appears to be extremely half-baked and (2) the new noise reduction.

The new noise reduction works. The lens profiles.. I've made one for my 28-300 which isn't great, but it gets me over the hump. I am trying really very hard to avoid doing things I know have been broken, and that means I do a lot more in photoshop (eg. the patch tool).

I don't know what to do anymore. This forum isn't working for me. I was after answers from Adobe. I'm getting none.

G

gtewks

Participant

I too, same issue.

HP laptop, windows 7, 4G RAM DD3, Duo Core i3 intell processor. And more importantly,,, never had any such issues on the very same files when i was running on my old computer (1G RAM, AMD 3800 processor)... which is like 1/3 the resource of the new laptop.

I even tried using the dust spot tool on a tiny little 50k file just to see what happens... Same thing.. still locks up for 30 seconds at a time every time I try and move the spot circle. Any computer within reason, with any processor or graphic card can handle that.

It seems all too clear with the wide variety of comptuers, and hevery processing power within these posts that the issue is a LR glitch and not our systems.

P

PleaseSir-t0QV4h

Participant

I'm having the same issue.

Surely it can't be my hardware as I am on a Mac Pro, 12Gb RAM, 8-core 2.8Ghz and just installed a fresh OS X. This is a huge PITA and rendering Lightroom unusable as I use the spot removal a lot for editing, nit just to remove dust spots bit to clean the image.

I hope Adobe fix this soon as I'm considering switching to Aperture 3. LR3 is great but it is rather slow.

A

Anonymous

Earth To Adobe... Come In Adobe...

why so silent? We've had one minor upgrade to Photoshop CS5, yet hasn't fixed the hard edges problem with your new technology "wonderful" hdr "pro" deghosting flop. (I've reported it you your official bug reporting system - nothing in response - not impressed).

Why so silent on Lightroom 3 and its issues? A prudent corporation worried about negative public opinion over such a major stuffup would have said something by now surely.

Very pissed off at lack of official response to these purported problems with LR 3.

You got what you wanted. Twice. You got my money for the LR 3 upgrade on the promise of better performance (which didn't happen), and for CS5 for the new HDR "pro", which is a flop. Did you take the money and run? Anyone there? Hello?

There's no nice way to say it - you messed up big time. You won't stay the king of the heap if you treat intelligent people this way.

nSonic-t5HfwJ

Participating Frequently

take a look at the memory usage.

i pretty sure, LR3 has a memory leak. I see the same problem with the brush tool and had hickups yesterday too.

After restarting LR3 everything is fine - for the next few pictures - before it's getting slow again (until it hangs)

web-weaver

Inspiring

Maybe - I'm not a computer specialist and I don't even really know what precisely a memory leak is or does.

I observed exactly the behaviour that you describe - that LR gets slow, then "hangs", then recuperates and then it gets slow again. But in my observation this recuperation is independent of re-starting LR or not. LR recuperates also just by waiting (boy - that's an exercise in patience!)

My observation is also that memory demand is not particularly high when this happens. I have 4GB of RAM but LR seldom gets up to 2 GB.

But my CPU is working like crazy: during the "hanging" or "freezing" of LR the CPU (dual-core at 3 GB) is at 100%.

Thus is seems to me that it's not a memory problem but a problem of too much "number-crunching" when using local adjustments (cloning-healing tool; adjustment brush; gradient filter).

I have a hunch that local adjustments are very difficult for a non-pixel based software.

ErnstK

A

Anonymous

I am hardly a computer expert, but it doesn't seem to me as though the basic functions of the cloning, adjustment brush and gradient tools have changed from LR2. Yes, when they work in LR3 they do seem to work more smoothly and quickly, but the end result seems the same and these tools in LR2 seem to work quickly enough on a decently spec'd machine (not so well on, say, a G5 iMac though). Maybe a case of "if it ain't broke....?"

A

Anonymous

You will find comments on this, including mine, elsewhere in this forum. I have similar problems with various functions in LR3, including with the cloning tool. Freezes, slowness, etc. Tried many, many things to see if I could fix, which I won't repeat here. Things seemed to get better and I can sometimes work for relatively long periods of time, and then the problem returns for a bit, and then goes away again. I will say that LR2 would occassionally get a little quirky for me and become unresponsive, but I would just close and reopen and it would generally go away. LR3 has been, and sometimes still is, something else again: absolutely unusable at times.

A

Anonymous

yep .. we've all been leaving a trail of cookies for Adobe to follow .. but not much back from them yet.

I'm gradually getting used to the slowness, the incessant screen size changing when cropping that can become maddening when you're trying to line stuff up, and the thinking moments mid- "spot removal" drag.

If you recall, LR2.1 was pretty bad, performance-wise, until Adobe "did something" and pushed out an upgrade.

(you see they've done this before... its a familiar pattern from Adobe)

And we're all running absolute beasts - so I don't think it much matters whether we compare 4 vs 6 vs 8 cpus.

We just gotta wait I guess.

M

mosscampion13

Participating Frequently

My CPU is an Intel Core 2 Duo E8500...so decently fast do you think?

I

Incredible_ShimmerB831

Participating Frequently

I am going to load the software[ Lr3 ]on a similar set up this week and see how it does.

--

Barry Liebowitz, M.D.

President, Doctors Council

http://www.doctorscouncil.com

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded