LIGHTROOM CC - Opening Catalog Settings results in severe disk thrashing

  • 2
  • Problem
  • Updated 4 years ago
  • (Edited)
When I open the dialog "Catalog Settings" and then the tab "File Handling" it takes a very long time (15 minutes), with lots of HD thrashing to determine the preview cache total size. My cache is 202 GB with 60,716 folders and 111,971 files, so I can understand how it might take a while. In fact, checking the parent preview folder properties in microsoft explorer takes quite a while. The problem is that if you close the "Catalog Settings" dialog Lightroom does not terminate the disk storage space process. This severely impacts performance until the process finally finishes. Subsequent attempts are much quicker as windows presumably caches the result.

Lightroom should terminate the process when the dialog closes if the user wishes to cancel.

Windows 7, LR CC
Photo of Rory Hill

Rory Hill

  • 242 Posts
  • 36 Reply Likes

Posted 4 years ago

  • 2
Photo of Martin Rosindale

Martin Rosindale

  • 34 Posts
  • 5 Reply Likes
Yes, I'm getting the same problem on my iMac and my catalogue is way smaller than Rory's. Never experienced this with LR5.7. It seems to be intermittent, I can't reproduce it on demand.

Beginning to get rather frustrated with LR6, I feel it should never have been released as there are far too many bugs and 'issues'.
Photo of Rick Hornsby

Rick Hornsby

  • 1 Post
  • 0 Reply Likes
I'm having disk thrashing issues with LR6 (OS X 10.10) without actually doing anything. I told LR to export some photos to Zenfolio the other day before going to work. When I got home LR was thrashing the disk.

I opened up LR about 10 minutes ago to do some work and it started the disk thrashing after about 2 minutes and hasn't stopped. Never had this problem in LR5. Never.

More info -

LR is idle - that is, I'm not doing anything in LR. But I've been watching LR's file activity for the last little while, it seems to be opening tons and tons of image files from the catalog. I can't really tell what it is doing though (trying to generate previews? doesn't seem to be) ... also, LR is calling /dev/urandom in a very serious way - 14,500 times in the last 5 minutes.