Jump to content

Lightroom 2.6 released but suddenly crashing importing M9 files


rebelfocus

Recommended Posts

  • Replies 62
  • Created
  • Last Reply

I have no idea if this is a related aspect of some fragility in the latest release, but from time to time I am getting an "Unable to read the full size image. There is an unknown error" message when opening some specific .dng's in ACR 5.6 via CS4/Bridge. The image preview appears OK in ACR, but before the yellow warning triangle disappears the warning pops up.

 

5.6RC worked flawlessly as far as I could see, but using 5.6 in a recent batch of very high ISO images (1650 - 2500) I get the warning message. I have to shut ACR down and try again and often it works next time, but sometimes it takes five or six goes. When it does stabilize the .dng is processed fine.

 

Steve

Link to post
Share on other sites

If I understan right I should uninstal my current Lightroom 2,6 version and then install the RC version. My question is - when I unistal Lightroom do I then loose all catalogs, development histories etc?? Will this be a problem for me if I uninstal and install the RC version??

 

Thanks for insights,

 

/Anders

Link to post
Share on other sites

I have been running the beta of Lightroom 2.6 and tonight the app notified me that the official 2.6 is out so I downloaded and installed it.

 

Now suddenly I find the app crashes reproducibly trying to import M9 DNG files. After the 15th one it crashes every time so am no longer able to get my images imported into the Lightroom catalogue. This wasn't happening with the 2.6 beta or 2.5.

 

Is anyone else getting this crash importing their M9 files into LR 2.6?

 

I'm having exactly this problem. Thinking of switching back to 2.5!

Link to post
Share on other sites

I haven't got to trying for workarounds yet. For speed reasons, I have been running LR in 64-bit mode for years and 2.6 RC was not crashing in 64-bit mode.

 

I have just posted a query on the Adobe LR forums. Another M9 user has already replied is seeing reproducible crashes not just on import but on several opening previously imported M9 DNG files in the develop module.

 

I switched to 32 bit mode and seems to work fine for now. At least it hasn't creashed in the first coupleof muinutes :-|

Link to post
Share on other sites

I have been running the beta of Lightroom 2.6 and tonight the app notified me that the official 2.6 is out so I downloaded and installed it.

 

Now suddenly I find the app crashes reproducibly trying to import M9 DNG files. After the 15th one it crashes every time so am no longer able to get my images imported into the Lightroom catalogue. This wasn't happening with the 2.6 beta or 2.5.

 

Is anyone else getting this crash importing their M9 files into LR 2.6?

 

Exact same thing happened to me. I switched to 32 bit...and no more problem!!!

Link to post
Share on other sites

Hi, I'm working on Mac OS X (10.5.8 Leopard), strangely I had the same problem when importing files from my M9, with Lightroom (version 2.5).

 

I tried it with the 'open in 32bit' box checked and unchecked, however LR wouldn't stop crashing. 10 days ago I didn't have any problems with LR (2.5) importing files from my M9, now I cann't import anything.

 

For me importing images with a card reader didn't work either. The only way I can import DNG files at the moment is with my D-Lux 4.

 

I'm really annoyed...:mad:

Link to post
Share on other sites

As a temporary solution LR 2.6 RC is available again from the Adobe site:

Lightroom 2.6 - Adobe Labs

Cheers,

Ario

 

Thanks for the info (I have the same problem).

 

Does anyone know, when the final fix will be available? As LR only crashes sometimes, I would not deinstall it and install RC if this issue is fixed soon.

Link to post
Share on other sites

Any news yet from Adobe?

 

As a general rule, Adobe don't issue patches outside of their regular 3-month update cycle. E.g., 2.5 had a bug that corrupted highlights for anyone using a G4 or G5 mac, and it wasn't fixed till 2.6. So best guess is that a fix is 2 months plus away.

 

Sandy

Link to post
Share on other sites

Yup, crashing here too :(

 

OS X 10.6.2 and running in 64 bits. After my latest import it is so bad that it now crashes immediately after opening. Stay well clear if you absolutely need 64 bits.

 

No problems in 32 bits.

 

Ditto. Crashing here too in 10.6.2. Lost 45 great Boxing day pics cross-country skiing with the wife, some friends and our dogs. Didn't explicitly set to 64 bits, but had 2.5 set for 64 bits, so the updater may well have preserved that.

 

[EDIT] Yes indeed, open in 32 bit mode is unchecked for the application, so that was carried forward.

Link to post
Share on other sites

Ditto. Crashing here too in 10.6.2. Lost 45 great Boxing day pics cross-country skiing with the wife, some friends and our dogs. Didn't explicitly set to 64 bits, but had 2.5 set for 64 bits, so the updater may well have preserved that.

 

[EDIT] Yes indeed, open in 32 bit mode is unchecked for the application, so that was carried forward.

 

How did a crash of Lightroom cause you to lose your pics?

Link to post
Share on other sites

How did a crash of Lightroom cause you to lose your pics?

FWIW I always copy my image files from the SD card to my prefered file location before I reformat the card. That way I know they are secure on my harddrive. I have learnt to have a healty mistrust of software that takes control over such matters.

Link to post
Share on other sites

How did a crash of Lightroom cause you to lose your pics?

 

That's a good question. I put the Extreme III 16Gb card in a USB reader and plugged it into my Mac. Opened LR 2.5, which said there was a new version (2.6) and would I like to install ? Said yes. It went through it's magic and then I restarted LR 2.6 and loaded in my pics. At about the 15th DNG, it crapped out. At the same time the mounted USB reader disappeared from my desktop. So I pulled out the USB reader and got the USB device ejected incorrectly error. When I put it back in, it had a corrupt data structure and I couldn't read anything from the FInder. Put it back in the camera, and I couldn't read anything either. Had to reformat it.

 

Moral of the story. Copy to a desktop folder first. Then you have a spare copy if something goes wrong I guess. Oh well.

Link to post
Share on other sites

That's a good question. I put the Extreme III 16Gb card in a USB reader and plugged it into my Mac. Opened LR 2.5, which said there was a new version (2.6) and would I like to install ? Said yes. It went through it's magic and then I restarted LR 2.6 and loaded in my pics. At about the 15th DNG, it crapped out. At the same time the mounted USB reader disappeared from my desktop. So I pulled out the USB reader and got the USB device ejected incorrectly error. When I put it back in, it had a corrupt data structure and I couldn't read anything from the FInder. Put it back in the camera, and I couldn't read anything either. Had to reformat it.

 

Moral of the story. Copy to a desktop folder first. Then you have a spare copy if something goes wrong I guess. Oh well.

 

 

Or do import initially with Adobe Bridge.

Link to post
Share on other sites

That's a good question. I put the Extreme III 16Gb card in a USB reader and plugged it into my Mac. Opened LR 2.5, which said there was a new version (2.6) and would I like to install ? Said yes. It went through it's magic and then I restarted LR 2.6 and loaded in my pics. At about the 15th DNG, it crapped out. At the same time the mounted USB reader disappeared from my desktop. So I pulled out the USB reader and got the USB device ejected incorrectly error. When I put it back in, it had a corrupt data structure and I couldn't read anything from the FInder. Put it back in the camera, and I couldn't read anything either. Had to reformat it.

 

Moral of the story. Copy to a desktop folder first. Then you have a spare copy if something goes wrong I guess. Oh well.

 

 

Ah, figured it had to be something like that. You've already come to the correct conclusion to prevent it happening again.

 

As for the corrupted SD card, did you try running Disk Utility on it?

Link to post
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...