Library freezes (2-3 sec) between Images, but Develop is Fast? (High-End PC: 3900X)
- November 4, 2025
- 4 replies
- 500 views
Hi everyone,
I'm at my wit's end with a Lightroom Classic issue (latest v15.0) and I've run out of ideas.
The Core Problem (The Anomaly):
My Library Module is incredibly slow. When I cycle through photos (in Grid or "Fit" Loupe view), the entire LrC interface hard freezes for $2-3$ seconds on every single image. During this freeze, I cannot click anything—the UI is completely unresponsive.
The weirdest part: my Develop Module is much faster. I can cycle through the same photos in Develop (using Smart Previews) with almost no lag. This is the complete opposite of how LrC is supposed to perform.
"The Freeze" Details (What happens in those 2-3 seconds):
When monitoring Task Manager during the Library freeze:
-
HDD/SSD: 0% active time (no obvious disk access).
-
GPU: 0-1% usage (not processing).
-
CPU: A small spike (around 10-15%), which on a 3900X (24-thread) suggests a single-core bottleneck or hang.
My System (It's not a slow PC):
-
CPU: AMD Ryzen 9 3900X
-
GPU: NVIDIA RTX 3090 (24GB VRAM)
-
RAM: 64GB
-
OS: Windows 11 (Fully updated)
-
Drivers: Latest NVIDIA Studio Drivers
-
Storage (Catalog/Previews): Fast M.2 SSD
-
Storage (Original Photos): Mechanical HDD (Slow)
-
Monitors: Dual setup (1x 4K as primary, 1x QHD as secondary)
The Files:
-
Canon R5 cRAW (Compressed RAW).
-
In one test, I noticed that uncompressed RAW files felt slightly faster, which makes me suspect a decompression issue.
What I Have Already Tried (The Long List):
Before you suggest "update your drivers," here is everything I've already done:
-
Solved GPU Conflict: Found and completely uninstalled Xtreme Tuner (GPU management software) which was causing a conflict.
-
Unlocked GPU: Deleted the Camera Raw GPU Config.txt. The new file now correctly shows gpu_compute_quick_self_test_passed="True".
-
Tested GPU: The AI Denoise function now works and pushes the GPU to 90-100%, proving LrC can use my 3090 for compute tasks.
-
Deleted Preview Cache: I deleted the entire ...Previews.lrdata folder (the one on my M.2) to start fresh.
-
Set 4K Previews: Set my Standard Preview Size to Auto (3862px) to match my 4K primary monitor.
-
Regenerated Previews: I have started the full regeneration for the entire catalog (it's ongoing, but the problem persists even on folders that are 100% complete).
-
Tested 2880px Previews: Before setting it to $4\text{K}$/Auto, I also tried using $2880\text{px}$ Standard Previews. The $2-3$ second freeze remained exactly the same, suggesting the preview size itself isn't the root cause, but that LrC is ignoring the previews entirely.
-
Disabled Auto-Corrections: I confirmed my default develop settings are "raw" (no Lens Corrections, Sharpening, or Noise Reduction applied on import).
-
Reinstalled LrC: I reinstalled LrC (keeping preferences).
My Theory
After all this, the Develop module is fast (correctly using Smart Previews from the M.2), but the Library module freezes.
This leads me to believe that the Library Module is ignoring my newly built Standard Previews (both $2880\text{px}$ and $3862\text{px}$) and is instead trying to read/decompress the original cRAW file every time, causing that 2-3 second single-core CPU hang.
Is this a catalog bug? Is it a cRAW-specific problem?
Has anyone ever experienced the Library being slower than the Develop module? How can I force the Library to only use the standard previews I just spent hours building?
Thanks for any ideas.
