Updating large LR4 catalog consumes all CPU/memory/locks up computer

  • 1
  • Problem
  • Updated 7 years ago
Updating a large (40k+ image) LR4 catalog to current process consumes all CPU/memory resources, more or less locks up computer.

I've done this ACCIDENTALLY now twice (by inadvertently pushing the update all button when meaning to convert to the 2012 process for a single image) and both times, I've not even been able to get the CTL-ALT-DEL dialog up to get to the task manager! So I've had to power off the computer.

4 year old lenovo machine with dual-core CPU, 4GB RAM.

I think that probably LR is gobbling up as much virtual memory as Windows will give it, but unfortunately the working set exceeds a reasonable size and it starts thrashing/paging.

Large updates to catalogs need to have some reasonable constraints on their memory usage. If it "only" asked for 1GB (on my computer) it would be fine.
Photo of Joseph N Hall

Joseph N Hall

  • 2 Posts
  • 0 Reply Likes
  • LR4

Posted 7 years ago

  • 1
Photo of Joseph N Hall

Joseph N Hall

  • 2 Posts
  • 0 Reply Likes
So, I'm doing a catalog in 10,000 photo "chunks," and it appears that the working set grows linearly (and extremely quickly) as the photos are processed. 10k photos gets me to a peak of 2.3GB working set in a matter of seconds, which is just about enough to start desperation paging.

Clearly you guys need to rethink something. This is obviously an operation that is made faster by gobbling up RAM but on the other hand you could do the background process update with very low memory usage as well.

I blame Windows for making it possible to lock up a computer by simply requesting too much RAM but still ....