Skip to main content
Adobe Photoshop Family

26 Messages

 • 

554 Points

Sun, Dec 11, 2011 7:00 PM

Lightroom: Spot Removal freeze (Win 7)

I have just bought Light Room3 (v3.5) on Dell Latitude E6520 with an Intel Core i7-2720QM processor, 8GB RAM and a 256GB SSD. I store my photos on a RAID5 NAS. When using the spot removal on .jpg files (so far it has not happened on raw - Nikon D7000 16MP .nef files) if use the tool more than twice in a row, LR freezes - the little hand makes a fist, processor works, memory used increases - looks like program is in a never ending loop). If I stop the program and re-start, the change is there. I notice on the web that this has been a problem for over a year but I cannot find a sensible fix. (There are many suggestions about bad drivers, bad power supplies etc.) Is there a fix? if so, what is it and where do I get it?

Responses

230 Messages

 • 

4K Points

9 years ago

Same here. I just installed LR 3.6 on my notebook (dual-core i7 2620M 2.7GHz processor with HyperThreading), Intel and NVIDIA video controller) and get the same (inconsistent, but repeating) results as in 3.5. This does not happen if I confine LR to Core0. Please note the HyperThreading in effect for both cores.

@Becky:
If I can assist with having debug traps in place, I'd be happy to test for you with your instructions.

Beat

130 Messages

 • 

2.1K Points

9 years ago

Just to add that after waiting in vain for over 10 minutes for my cursor to come back inside Lightroom, I used the Task Manager to assign affinity to one core only and got immediate recovery of the cursor AND the ability to rapidly and smoothly add many more long-distance spot removals.

BTW, I did not have to be zoomed into 1:1 for any of the above problems....they happen just the same in Fit view.

230 Messages

 • 

4K Points

9 years ago


after waiting in vain for over 10 minutes for my cursor to come back inside Lightroom, I used the Task Manager to assign affinity to one core only and got immediate recovery of the cursor AND the ability to rapidly and smoothly add many more long-distance spot removals


This is what I'm experiencing also. Assigning affinity to one core immediately solves the "lock". Also, I've never had to kill LR to recover, it always came back by itself after a (varying) while (but I'm a patient IT person :-))

Beat

26 Messages

 • 

554 Points

It is possible to solve the 'lock' by just un-assigning the correct core - which is usually the one that is consistently busy. Cores are numbered starting at 0 from the left in the performance window in Task Manager

130 Messages

 • 

2.1K Points

9 years ago

George, I think you'll find that it doesn't really matter which single core you assign affinity to, it's just the fact that a single core is assigned which causes LR to 'unlock'. I've assigned both inactive and active cores with the same result.

26 Messages

 • 

554 Points

Hi Jim, I think you misunderstood. If LR is assigned to multiple cores and 'lock's up', by looking at the core activity under Performance and un-assigning the core which is busiest, 9 times out of 10 LR unlocks at the point you hit the OK button. Oddly stopping the core seems to have no detrimental affect on LR which continues as normal, and displays the change being made at the time of the 'lock-up' as being completed.

I would tentatively interpret this as one thread being stuck in a loop waiting for 'something' to signal completion when in fact the 'something' has already completed but the looping thread is not recognising this and is in turn holding up the completion of another process/thread.
I suspect this condition depends on the timing between two threads which is why it happens so illogically in one machine with a specific photo but not on another, This is just a guess but if correct means that adding debug code will probably stop the lock-up from happening on the same machine under the same conditions. It is not easy to find.

I have seen times when LR is locks up for 10 or 15 secs and then reverts to normal behaviour - in this case if the task manager is open you can see the usage on one core drop from about 85% to a normal 0-1% at the point that LR unlocks.

130 Messages

 • 

2.1K Points

OK, yes I see what you are saying.....except that (certainly in my case) when it "locks up" there are usually 3 or 4 cores which are 'busy', so pinpointing the 'one' to clear the hang becomes a matter of trial and error. In my case it is far simpler to simply reassign to a single core just to clear the problem.

One of the other inconsistencies that I've mentioned is that the length of time that LR "locks up" can vary from seconds to more than a few minutes. Also, it seems that the problem only occurs when one attempts to 'drag' either of the two circles.....

26 Messages

 • 

554 Points

I would agree with you about the inconsistencies but think I am more impatient than you - if it freezes for more than about 30 seconds, I'm too impatient to wait - so I don't know about it recovering after a few minutes. I notices in LR3.6 it was more likely to recover (within my limited attention span) than with 3.5.1.

130 Messages

 • 

2.1K Points

In a real-life situation I also would be far more impatient, I've let it 'hang' for minutes at a time only as part of a targeted testing effort in order to provide as much information as possible to the Adobe engineers and the folks over at Lightroom Forums.

3 Messages

 • 

80 Points

9 years ago

More than one person has confirmed that the problem is happening when all of the following conditions are met:

- JPEG image
- Core i5 / Core i7 CPU
- Hyperthreading enabled

Disable hyperthreading and the problem does not occur, or at least not as often.

With only one core assigned forcibly to LR process the problem never occurs.

See this thread (which has been running for 1.5 years now):

http://forums.adobe.com/message/40913...

26 Messages

 • 

554 Points

Hi uncle_fed,

Given the number of people who are suffering from this problem and who have complained about it on other fora, I'm surprised that the little counter at the top of this thread still says '2 people have this problem'. I have worked in the IT business for the last 23 years and I know how difficult it is to find something like this (not that problems like this could exist in PCs 23 years ago) but I also know that if only a small number of people complain about it, then it may never get to the top of the pile to be looked at.

George

230 Messages

 • 

4K Points

Very good point !!!

26 Messages

 • 

554 Points

Hi Beat, Do you know how to add a comment to the above thread - I can find no way to do it. Do you need to log in a second time for a button to apear or something?
George

230 Messages

 • 

4K Points

If you're refering to the thread at the Adobe Lightroom forum (http://forums.adobe.com/community/lig...:
You need to sign in using the "Login/Register" link right underneath the large title 'Forums".

Beat

1 Message

 • 

60 Points

9 years ago

I am having the same problem myself.
The problem has been described well enough here and elsewhere, so not going to bother repeating everything, lest just add that I too am suffering from this bug, and hope Adobe can fix it ASAP.

(I am aware of the 'fix' of changing CPU affinity, but I find that a wholly unsatisfactory solution. I shouldn't have to hamper my computer/software to circumvent something that is most assuredly a bug.)

Helge

26 Messages

 • 

554 Points

9 years ago

As an experiment over new year I installed LR3.6 onto my wife's computer - same make/model as my own but more modern - and had exactly the same hanging problem with spot removal.
George

9 Messages

 • 

186 Points

9 years ago

Sorry to be late to this party, but I have struggled with this problem for a several months. For me, it happens with 16-bit tiff files created by LR 3.6, externally edited (Ctrl+E) in PS CS5, and automatically added to the catalog by LR after editing. Don't recall if it happens with raw (CR2) files or not. Camera is Canon 5D2.

FWIW, here is some system info reported by Windows (sorry for the mess below):

System:
OS Name: Microsoft Windows 7 Professional
Version: 6.1.7601 Service Pack 1 Build 7601
System Type: x64-based PC
Processor: Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz, 3334 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date: American Megatrends Inc. 0701, 10/05/2011
SMBIOS Version: 2.5
Hardware Abstraction Layer: Version = "6.1.7601.17514"
Time Zone: Eastern Standard Time
Installed Physical Memory: 24.0 GB
Total Physical Memory: 24.0 GB
Available Physical Memory: 17.6 GB
Total Virtual Memory: 48.0 GB
Available Virtual Memory: 40.0 GB
Page File Space: 24.0 GB

Graphics:
Name: NVIDIA GeForce GTX 260
PNP Device ID: PCI\VEN_10DE&DEV_05E2&SUBSYS_0CFB19F1&REV_A1\4&2F1C4782&0&0018
Adapter Type: GeForce GTX 260, NVIDIA compatible
Adapter Description: NVIDIA GeForce GTX 260
Adapter RAM: 896.00 MB (939,524,096 bytes)
Installed Drivers: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,
: nvd3dum,nvwgf2um,nvwgf2um
Driver Version: 8.17.12.7533
INF File: oem36.inf (Section005 section)
Color Planes: Not Available
Color Table Entries: 4294967296
Resolution: 1920 x 1200 x 59 hertz
Bits/Pixel: 32
Memory Address: 0xFA000000-0xFAFFFFFF
Memory Address: 0xD0000000-0xDFFFFFFF
Memory Address: 0xF8000000-0xFBCFFFFF
I/O Port: 0x0000CC00-0x0000CC7F
IRQ Channel: IRQ 24
I/O Port: 0x000003B0-0x000003BB
I/O Port: 0x000003C0-0x000003DF
Memory Address: 0xA0000-0xBFFFF
Driver: c:\windows\system32\drivers\nvlddmkm.sys (8.17.12.7533, 12.59 MB (13,206,120 bytes), 21/05/2011 6:01 AM)

26 Messages

 • 

554 Points

9 years ago

Hi Richard, Thanks for the info, I hope Becky and/or Jeffrey will find it useful. Nothing has happened over Christmas and new year, Cheers George

1 Message

 • 

72 Points

9 years ago

LR 3.6 Spot Removal Tool hangs the program. But of course you already know this. It's been a problem for at least 1 1/2 years - based on forum comments. Anyway, please fix at least by LR4 release.

This reply was created from a merged topic originally titled
Lightroom 3.6: Spot Remvoal Tool hangs application.

130 Messages

 • 

2.1K Points

9 years ago

From some initial testing in the LR4Beta it would seem the problem may well be fixed in that release.

230 Messages

 • 

4K Points

My tests also don't show the symptoms anymore on my available computers with LR4 Beta.

Beat

1 Message

 • 

72 Points

I also have not had a problem using LR4beta
Gary

3 Messages

 • 

80 Points

The only problem with LR4 is that it is LR4, not LR3. Which means that to get the issue fixed we will have to pay $$ in the end.

230 Messages

 • 

4K Points

Some people can never be satisfied :-(

3 Messages

 • 

80 Points

I will be satisfied as soon as the product I paid for will work as advertised. Is there anything wrong with that?

4 Messages

 • 

92 Points

I do agree that fixing a bug in the product should not come at the cost of the user. If the "fix" can't be applied to LR3, then refunds or rebates need to be issued to those with the problem. (Or free/discounted downloads of LR4)

7 Messages

 • 

154 Points

9 years ago

Lightroom keeps freezing and stops responding when I use the spot removal tool 60% of the time I have to shut down Lightroom using the task manger and then reopen. Any solutions. This was happening in Version 3.5 as well as 3.6

This reply was created from a merged topic originally titled
Lightroom freezes up using healing brush.

1 Message

 • 

62 Points

9 years ago

George and Beat -

While it's a very frustrating problem that needs to be fixed, your detailed investigation is incredible. Thank you for your focus and posting your findings and how do "resolve" by managing CPU affinity settings.

I'm encouraged to see LR4 appears to fix it, though share the concern that it should be fixed in an LR3 update rather than having to wait, then buy the LR4 production release.

26 Messages

 • 

554 Points

9 years ago

Hi Sue,
I too would like to see it fixed in an LR3 update but I do undersand that this may not actually be possible (depending on what had to be changed, the 'fix' may not be backward compatible) However I am hoping that the cost of the up[grade may be minimal. I am however heartened by the amount of discussion this has stimulated. I may still have the problem, but I no longer feel alone with the problem.
Cheers
George

4 Messages

 • 

92 Points

9 years ago

George, thank you for being so persistent with this. Because of your work I have at least gained a tremendous amount of information about this problem and similar instances. Too bad there doesn't seem to be a fix that will be applied to LR3...