Out of Memory error end erratic behavior

Brief description of the issue: while importing images at their current location, some of them would show in grid view with an exclamation mark, and LR would not allow me to adjust them. Removing and importing the same set of images again, the subset of troubled images changed. At some stage, trying to develop one of the images, I got an ''Out of Memory'' written in red in the center pane. PS CS opens the same images without any problem, and Windows Task Manager indicates there is plenty of available physical and virtual memory.



Here what I did in detail.



While I was importing images at their current location into the library from DVDs, I started to see en exclamation mark in the upper right corner of several images in the grid view. When I selected any of those images and hit ''D'' to develop them, I got ''An unknown error occurred'' in the Develop module, and LR would not allow me to do any adjustment.



I have tried removing the images from the Library and importing them again, and then some of the troubled images were not the same as before, and LR would allow me to develop some of the previously troubled images.



PS CS File Browser shows them all correctly, and also PS can open any of the images without any issue.



I have copied some of the troubled images to my hard disk, and then tried to import them into LR from there. The same image sometimes worked, sometimes didn't. Finally, when trying to develop one of those, I got an ''Out of Memory'' error message printed in red and upside down in the middle of the picture.



Windows Task Manager was reporting 833824 KB of Available Physical Memory out of 2095536 KB, and was reporting as Commit Charge: Total 1281084 KB, Limit 5080272 KB, Peak 1707720 KB.



Any idea what is going on? It looks to me like instability after I imported a few hundred pictures in a row.
Out of Memory error end erratic behavior
It's a bug that the team is working on. For now, the cure is to restart LR.
Out of Memory error end erratic behavior
Lee,

Thanks for the update. When I went to adobe support, they wanted to believe it was not a problem. I'm looking forward to v1.1

:-)

Patrick

Was having this a LOT this weekend. Also a LOT of 'These photos failed to import' and 'these photos failed to export' with NO explaination of what went wrong. Lightrooms Error messages plainly suck, they simply dont give you enough information to trouble shoot with. The only conclusion I can come to is that this software is to blame and not anything I or my machine do wrong. Repeated attempts to do the same process all fail. Fortunately restarting the application fixed it, but it is VERY frustrating and completely undoes what little confidence I had in the app.



Sam

Like I said, Sam, it's a bug and restarting the application is the present fix. The team is well aware of this issue.

Sam -



One thing I noticed on your export errors - I got this when I had set up an export whose end action was to open the folder in explorer (windows). If I already had that folder up in explorer - the export would error out every time - saying certain images were not exported successfully. If I made sure that I closed this explorer window down prior - then the export would work - no restart required in this particular case. Not sure if this is something known or similar to your export problem - but I thought I would mention my particular experience just in case.



Also - I watched the memory usage of LR while I was working yesterday within the program - and with the stuff I was doing - meta data updates, a bit of work on cropping, exposure across a few hundred images - I saw memory increase gradually until I too got that memory error message when I tried go into loupe view on an image.



I would imagine this is the bug that Lee Jay says the team is well aware of.

You can get the upside-down OOM error when plenty of system memory is available.

Right after the Out of Memory issue, I removed the incriminated images from LR Library, and directed LR to remove a keyword with count 0 from the left panel; LR gave me ''Attempt to yeld across methamodel/C-call boundary'' and did not remove the keyword. Ouch!



Re-starting LR apparently resolved the issues I was having.

You are ABSOLUTELY right that I had explorer windows open when I got the export failed messages!!!! I do all my printing at costco, so I have Lr export my final pics to a 'jpeg finals' directory, and then individual sub-directories for each folder they came from, and then manually copy from each of these sub directories to the root directory on my CF card for transport to Costco.



Will see if it happens in the future without that window open. Still wouldnt help the upside down OOM messages, tho thanks for the update that the team is working on it.



These two issues and the UI lag are really all that I can ***** about too much, which is pretty amazing given my beta frustrations. I still wish I wasnt locked to the DB. I still cannot in good conscience recommend Lr to most new DSLR users. But for my own use I'm pretty happy. I wish I could get better highlight and shadow recovery like I got in RSP but I'm sure that is user error and n00bishness more than a failure of the app. I'm also not happy that I can't toggle the crop tool to the way I want to work permanently but I guess that ship has sailed too.