I have a problem, certain tiff/psd files, when selected, will crash LR 3.5 64bit Windows 7, this did not happen in previous versions of LR 3. Seems to be my B&W scans, it looks like any tiff/psd, with photoshop adjustments (layers), that have been further modified in lightroom are the cause. I have tweaked a lot of my photoshop files in LR after doing layer work in PS, this needs a fix ASAP. I have seen others mention a similar problem.
It may well be, however, further information for you, it seems it is dot gain profiles, some of which open fine others not, about the only difference is, I modifed the one that crash in CS 3, there may be several layers, tochup, curves etc... nothing fancy. I then may have tweaked these again in lightroom. If I delete from catalogue and re-import, it still crashes LR, so maybe not related to further tweaks in LR. If I convert to say RGB in CS 3, they do not crash LR when imported, I covert back to dot gain in CS 3, they again crash LR. This did not happen in LR 3.4, only since upgrading to LR 3.5. Hope that helps.
It has been almost a month since this crash was introduced into LR 3.5 when is there going to be a fix? Or explain how the problem can be resolved, this did not happen in LR 3.4. It is now holding me up work wise, and I have had to rescan images and process them. This is not an option for all images, I have many that cause the crash.
I have just installed 3.6RC and this did not resolve the problem. As soon as I select a B&W photograph (as described above) LR crashes. The only way I can resolve the crash is to open the image in PS, covert to RGB, LR does not crash. This is not what I want to do as my photos are B&W scans, I would like some support on this issue to resolve the problem as it is holding up my work flow. The problem must be due to dot gain, this did not happen in LR 3.4 or prior versions of LR 3.
OK, this is fairly stright forward to reproduce, B&W scan, dot gain colour space, use the burning brush to modify image, crash. Come on, I have been stuck with this bug for months now, it is about time there was a patch to resolve the issue. This is now seriously affecting my work flow, I am not far off moving to Apple's Aperture.