Lightroom: Spot Removal freeze (Win 7)

I'm using two monitors - both are full HD (1920 * 1080) with an nVidia card (sorry not at home so don't know the exact version). My feeling is that it's not this as I updated all drivers about 2 months ago - I only have LR3 a couple of weeks. Nothing else freezes when this happens, any other program running works normally and I can see the memory in use by LR3 increasing.

Its possible my comment above only demonstrates my ignorance of how LR3 works. I'll try this and the other possible solutions tonight. Thanks for the reply, I'll keep you posted..

Same exact scenario to George, very similar hardware, monitors, nVidia GTX 560 Ti, brand new and updated. 16 GB of RAM, AMD FX(tm)-6100 Six-Core processor, SSD drive for OS and 2TB hard disk for media. This occurred on our last machine as well, which wasn't quite as powerful.

I have noticed that it is more frequent when working on files that I had edited in photoshop and then saved as psd. Also tried operating the catalog on both drives, SSD and hard disk, no change.

George,

If you want to try if setting LR to only use one core, here are the instructions on how to set processor affinity for a process:
http://www.addictivetips.com/windows-...

I'd be interested in hearing your results.

Beat

Thanks - I'll post my results in a moment - I think it is a thread problem :-)

If you give me an e-mail address or access to an ftp server, I can let you have a copy of the image and detailed instructions on how I get it to freeze.

Thanks for your findings, George, which match what I experience, although I did not go that far with testing.

Beat

Hi Becky,

This is the same problem you and I discussed directly when V 3.0 was released. With each passing update I hoped, as did you, it has been resolved but through 3.5 no solution seen yet. There was some improvement around 3.2 or 3.3, I don't remember, but it is still there.

It seems fairly certain to be a core resourcing problem. I have turned hyper-threading off and the problem/lag is significantly better (as other have suggested) and it is clearly worse on JPEG images (again, nothing new being reported). When I do still see the spot-healing hang, or if I visit an image in the Develop Module which had a significant number of spots previously applied, I view the "CPU Usage" gadget I have running and always when this hang occurs, one core (random) is always at 100% and feels "stuck". As soon as it drops down below 100%, all goes back to normal.

I haven't loaded 3.6 as there was no indication that this issue was worked on since 3.5 thus I saw no need. Others don't seem to see any improvement either so I assume it is still the same old issue. I have tried both Nvidia and Ati cards and updated software but the problem persists.

Hopefully when version 4.0 comes around with the much sought-after healing brush they have figured this out since it is likely to be much more computation intensive than the spot healing tool :)

Best of luck tracking this down.

Jeff

and always when this hang occurs, one core (random) is always at 100% and feels "stuck"

Jeff,

This is not what I (and others who have tested) see during the lockup. This is a snapshot of my CPU usage during such a lockup, note that the hang was resolved where you see the sharp decline in CPU usage on several cores.

Beat

Beat - and that is probably why this problem has persisted so long, it can't be consistently described or duplicated between machines. Do you have the i-5/7 cores or the Xeon series? I have the Xeon E5520 2.27GHz processors (2).

Jeff

Jeff,

This screenshot (from above) was taken on a i7 980X with Hyperthreading enabled. But I also see similar behaviour on my notebook with an i7 2620M with Hyperthreading enabled (see here).

Disabling Hyperthreading seems to cure the problem on my i7 2620M (2 cores left), but not on my 980X (6 cores left), as this screenshot shows. Note that when Hyperthreading is off, one core is close to (but not AT) 100% during the lockup period.

Beat