New Lightroom Update (v1.4) - Warning!

[Michael Garner]

I would recommend proceeding with caution.

This morning, I updated to Lightroom 1.4 as well as ACR/DNG 4.4. I am now experiencing serious problems.

Problem 1: Update DNG Preview & Metadata
When I perform this operation, Lightroom warns that the step did not complete successfully. The DNG file is now damaged and cannot be manipulated in Develop or in ACR

Problem 2: Edit Phot  with Adobe Photoshop CS3
When I perform this operation I receive a messate that Lightroom was unable to prepare the selected file {file location} for editing. it wil not be opened.

I can't say for certain that the release is flawed (as this are rather egregious errors to slip through QA). It is entirely possible that I have done something wrong and I am researching this now.
But for the moment, I would be concerned about applying this update.

Regards,
Michael

P.S. If anyone has any ideas about how to repair damaged DNGs, I would appreciate the info.

[Michael Garner]

I performed an installation repair. The edit in CS3 problem seems to have gone away. But I still have the problem with updating the DNG preview and metadata.

Now, I am not getting the error message when performing the operation but after it is complete, the color label has changed from "none" to "red" (red was the original condition on import). When I move to the develop panel, the image shows "An unknown error has occurred"

Once I have run this step and damaged the DNG, I cannot perform the edit in photoshop (which creates a PSD version), nor can I do anything in ACR (it opens the DNG but shows errors and won't allow edits).

And it started our as such as nice day.

Michael

[peterkrogh]

Michael,
1. Do you have a backup of the DNG?

2. Let me get this straight - you had DNG files that you assumed were fine. You pushed metadata out to the DNG files and the operation choked.  Now ACR can't open the files.

Have you checked more than one file?

Can you test on a duplicate set of known-good files?  It would be good to know if you can pinpoint this corruption.  (I want to make sure this is not an unrelated error that is just coming to light right now.)

Can you supply the relevant specifications (filetype, OS, other relevant details.)

Peter

[Braders]

Peter, there is a concerted effort as we speak on the lightroomforums

http://www.lightroomforums.net/showthread.php?t=1475

[Michael Garner]

Peter,
1) Yes, I have backups of the original RAW files and the DNG images prior to the LR 1.4 upgrade. I have already restored the damaged files so no data loss.

2) Yes. The DNGs were fine. I can go back to any of the DNGs and load them directly into CS3. Once I perform an "Update DNG preview & Metadata", the file displays "An unknown error occurred" in the Develop module and I can not load the file directly into CS3 (nor can Lightroom create a copy and edit in CS3).

I have tested dozens of files in different sets. I see the same behavior every time. Take an existing DNG. Import into Lightroom. I can invoke CS3 from Lightroom (creating a PSD version). I can open the file directly in CS3 (through ACR). As soon as I attempt to touch the DNG in Lightroom (update metadata, preview), it is damaged and can't be read by LR/ACR.

System: Windows Vista Ultimate
Image Source: Nikon D200
Basic workflow steps:
1) Images are ingested using ImageIngester Pro  (Original RAW is written to a backup drive)
2) ImageIngester performs the DNG conversion   (Converted DNG is written to a working drive)
3) Importing into Lightroom is manual (drag and drop folder into Library)
4) All working drive data, Lightroom catalogs, Expression Media catalogs, etc are backed up nightly

Since I performed the Lightroom upgrade first thing in the morning, all of the previous days work was backed and nothing has been lost.

Thanks,
Michael

[peterkrogh]

Here's some more information on this.

This is a Windows-only bug, having to do with LR 1.4 and DNG converter 4.4

The issue is now known, and on its way to be fixed very soon.  DNGs can be repaired by running them through the 4.3.1  DNG converter.  Ideally, it's better to reconvert from the previous file (either raw or DNG), due to another metadata glitch having to do with EXIF time.  (I'm not sure how this problem manifests).

If you're on Windows, it's best to retrograde to 1.3 until this is resolved.

Peter

[Craig Murphy]

How would one go about retrograding once you have done the upgrade?

[ptr727]

I was reviewing some old images and LR 1.4 crashed whle reading one of the images.
If I restart LR and point it to the same folder it crashes again.
All these images were taken with my Cingular 8525 Pocket PC phone at a concert event.
I experimented and removed all images from the drive, leaving them in the LR DB, then adding them back one by one.
One particular image always crashes LR, some images report failure reading image, then after a few seconds they load fine.
If I delete one of the images without problems from the DB, then add it back, LR crashes.
So it does not seem to be a specific image, but rather something generic about the images.

The last time I reviewed these images were quite some time ago.
The machine I used then was Vista Ultimate x86, and LR was 1.3.0.
I am now using Vista Ultimate x64 SP1 and LR 1.4.
So it is not ecessarily LR, but no other editor has problems with the files, only LR, so I expect LR 1.4 is to blame.

Here is a stack dump:
FAULTING_IP:
CameraRaw!AgWatermark_load+163d3
00000000`60629093 8a11            mov     dl,byte ptr [ecx]

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000060629093 (CameraRaw!AgWatermark_load+0x00000000000163d3)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000009fbb270
Attempt to read from address 0000000009fbb270

FAULTING_THREAD:  0000000000000fcc

DEFAULT_BUCKET_ID:  APPLICATION_FAULT

PROCESS_NAME:  lightroom.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

READ_ADDRESS:  0000000009fbb270

BUGCHECK_STR:  ACCESS_VIOLATION

APPLICATION_VERIFIER_FLAGS:  0

LAST_CONTROL_TRANSFER:  from 0000000060632849 to 0000000060629093

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
0a62c4e4 60632849 09f69da8 00000004 60632924 CameraRaw!AgWatermark_load+0x163d3
0a62c54c 606a5132 00000001 0a62e7e0 098a09d0 CameraRaw!AgWatermark_load+0x1fb89
0a62e454 606aeba4 0a62e7e0 098a09d0 00000101 CameraRaw!CTJPEGRotateImage+0x71ed2
0a62e7c8 60619552 0a62e7e0 098a09d0 0a359388 CameraRaw!CTJPEGRotateImage+0x7b944
0a62e870 60785c1f 07bf8500 0a62e89c 00000005 CameraRaw!AgWatermark_load+0x6892
0a62e900 60f9b280 0a359388 00000000 0a359388 CameraRaw!ReadThumbnailAndOrientation+0x5b6f
0a62e930 60fa1845 0a359388 0a386520 ffffffff substrate!luaopen_package+0x4080
0a62ed74 60f9b55e 0a359388 60fa1830 0a62edd0 substrate!lua_error+0x65
0a62edd8 60f9b280 0a359388 0a359388 0a386510 substrate!lua_yield+0x1ae
0a62eed8 60f9b387 0a359388 00000005 00000090 substrate!luaopen_package+0x4080
0a62eef0 60fa1845 0a359388 0a360158 ffffffff substrate!luaopen_package+0x4187
0a62f334 60f9b55e 0a359388 60fa1830 0a62f390 substrate!lua_error+0x65
0a62f398 60f9b280 0a359388 0a359388 0a360148 substrate!lua_yield+0x1ae
0a62f490 60f9b387 0a359388 00000002 00000048 substrate!luaopen_package+0x4080
0a62f4a8 60fa1845 0a359388 0a3600f8 ffffffff substrate!luaopen_package+0x4187
0a62f8ec 60f9b55e 0a359388 60fa1830 0a62f948 substrate!lua_error+0x65
0a62f950 60f9b280 0a359388 00000020 0a359388 substrate!lua_yield+0x1ae
0a62f980 60fbabb8 0a359388 0a3600e8 ffffffff substrate!luaopen_package+0x4080
0a62fa88 60f9b387 0a359388 00000001 00000000 substrate!AgLua_callWithAutoReleasePool+0x78
0a62faa0 60fa1845 0a359388 0a359500 00000000 substrate!luaopen_package+0x4187
0a62fee4 60f9b55e 0a359388 60fa1830 0a62ff48 substrate!lua_error+0x65
0a62ff54 60fb5b6b 0a359388 00000002 00000000 substrate!lua_yield+0x1ae
0a62ff88 7718e3f3 09936068 0a62ffd4 7762cfed substrate!AgTaskStatusLink_optFromLua+0xa6b
0a62ff94 7762cfed 09936068 7dfd6027 00000000 kernel32!BaseThreadInitThunk+0xe
0a62ffd4 7762d1ff 60fb5b20 09936068 00000000 ntdll32!__RtlUserThreadStart+0x23
0a62ffec 00000000 60fb5b20 09936068 00000000 ntdll32!_RtlUserThreadStart+0x1b


FOLLOWUP_IP:
CameraRaw!AgWatermark_load+163d3
00000000`60629093 8a11            mov     dl,byte ptr [ecx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  CameraRaw!AgWatermark_load+163d3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CameraRaw

IMAGE_NAME:  CameraRaw.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  47d06159

STACK_COMMAND:  ~15s ; kb

BUCKET_ID:  X64_ACCESS_VIOLATION_CameraRaw!AgWatermark_load+163d3

FAILURE_BUCKET_ID:  CameraRaw.dll!AgWatermark_load_c0000005_APPLICATION_FAULT

Followup: MachineOwner
---------

Here are some sample images:
http://www.insanegenius.com/download/LR.1.4.Crash.zip

Should I try to report this to Adobe, or is it like many large ISVs a fruitless endeavor?


Regards
Pieter

[havezet]

I came across this today:

http://blogs.adobe.com/lightroomjournal/2008/03/important_lightroom_14_and_cam.html

Adobe recognizes the problems with 1.4 and recommends to deinstall it (also seem to apply to ACR 4.4)

Hert

[ptr727]

I can confirm that after reverting to 1.3.1, LR no longer crashes when viewing the images I referred to in my previous post.

Regards
Pieter

[peterkrogh]

Yes, the retrograde to 1.3 is recommended for everyone.
Peter