Lightroom 3.3 hangs in develop module.

Question

Hi,
I've been a long-time user of lightroom. I've recently replaced my graphics card (from 9500GT to 450GTS) and I'm starting to see quite frequent apphangs. I never saw these before the change in graphics card, but I did change it a couple of weeks ago and I only started seeing these crashes on 31/3. Having said that, I haven't used LR for a few weeks, so this still might be consistent. As far as I can tell, it only happens when LR is in the develop module and most of the time it's when LR is loading an image, the spinning disk freezes and the program hangs requiring a kill/reboot. I've also seen it today with a sharpen operation though. The hang is random - I can do exactly the same sequence of operations on the reboot and they work fine. The symptoms are very similar to the ones a lot of people reported a few years ago with LR 2 although thge suggested fix there (switch to develop->quit->restart) doesn't seem to improve stability.  I have the latest Nvidia drivers, and the machine is rock solid apart from this problem. I've tried LR 3.4 beta and that still exhibits the problem.
Anyone else seen this? Anyone know of any workarounds - it's pretty frustrating - it can be anywhere from 30 seconds to 30 minutes before it happens?
The signature of the problem is:
Version=1
EventType=AppHangB1
EventTime=129468332725694479
ReportType=3
Consent=1
ReportIdentifier=7b6113c3-62b6-11e0-ae0e-bcaec5991709
IntegratorReportIdentifier=7b6113c4-62b6-11e0-ae0e-bcaec5991709
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=lightroom.exe
Sig[1].Name=Application Version
Sig[1].Value=3.3.0.10
Sig[2].Name=Application Timestamp
Sig[2].Value=4ce58483
Sig[3].Name=Hang Signature
Sig[3].Value=979b
Sig[4].Name=Hang Type
Sig[4].Value=513
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=979bf393bed3406173114ae9a115a41d
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=3ce7
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=3ce7386b5e35e43013e6ea065fa68452
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=979b
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=979bf393bed3406173114ae9a115a41d
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=3ce7
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=3ce7386b5e35e43013e6ea065fa68452

Answer 1

Hi Dan,
OK, so now I'm confused... I have removed the profiles for the monitors (one for each) and now use the manufacturer supplied one and haven't been able to get a crash since yesterday when I did the change. I'm not 100% confident the bug has gone, but it's passed my "it should happen by now" criteria. I'm wondering if the size of the .icc profiles could have an influence. When I calibrate my monitors, I always do a full calibration which stores the data as a full LUT iccview.de lists it as:
Description Tag:
Monitor_2_17-03-2011
ICC-Tag: BToA1 (Colorimetric)
Calculation: LUT with 35937 grid points
Header:
size = 690296 bytes
CMM = 'APPL'
Version = 2.4.0
Device Class = Display
Color Space = RGB
Conn. Space = XYZ
Date, Time = 17 Mar 2011, 15:50:32
Platform = Microsoft
Flags = Not Embedded Profile, Use anywhere
Dev. Mnfctr. = 0x0
Dev. Model = 0x0
Dev. Attrbts = Reflective, Glossy
Rndrng Intnt = Perceptual
Illuminant = 0, 1, 0 [Lab 100, 0, -0]
Creator = 'LOGO'
Total volume of gamut is 885574 cubic colorspace units
The profile I have moved to and which seems to be working is a much smaller matrix profile. iccview.de says:
Description Tag:
DELL U2410 Color Profile,D6500
ICC-Tag: XYZ Matrix
Calculation: 3x3 Matrix
Header:
size = 6756 bytes
CMM = 'ADBE'
Version = 2.0.0
Device Class = Display
Color Space = RGB
Conn. Space = XYZ
Date, Time = 1 Mar 2010, 14:15:19
Platform = Microsoft
Flags = Not Embedded Profile, Use anywhere
Dev. Mnfctr. = 'DELL'
Dev. Model = 0x534654
Dev. Attrbts = Reflective, Glossy
Rndrng Intnt = Perceptual
Illuminant = 0, 1, 0 [Lab 100, 0, -0]
Creator = 'DELL'
Total volume of gamut is 1401609 cubic colorspace units
So, assuming I get no more crashes, how do you want to debug this further? Do you want my icc profiles?