Skip to main content
Participant
September 21, 2026
Question

Lightroom Desktop 9.5.1 on macOS: Square Grid Camera Raw preview memory leak peaks at 45.6 GB and thrashes swap

  • September 21, 2026
  • 1 reply
  • 13 views

Incident date: 21 September 2026. This was measured during a production editing session, not a synthetic stress test.

Product and environment:
- Adobe Lightroom Desktop (cloud-based) 9.5.1 arm64 [20260815-1945-84a45bf]
- macOS 27.0 (26A428)
- Apple M3 Pro with 18 GB unified memory
- Canon CR3 originals stored on an external SSD
- Approximately 134 GB free on the internal drive and 65 GB free on the external drive
- No macOS thermal or performance warning was recorded

Summary:
While viewing a filtered set of edited CR3 files in Square Grid, Lightroom’s Camera Raw preview-rendering pipeline accumulated tens of gigabytes of memory and eventually made both Lightroom and macOS nearly unusable. Relaunching Lightroom immediately returned memory usage to normal with the same files and hardware.

Steps observed:
1. Open a local folder containing approximately 9,064 CR3 files.
2. Apply the Blue color-label filter, leaving 417 photos visible and 8,647 filtered out.
3. View and scroll through the edited RAW thumbnails in Square Grid.
4. Lightroom progressively becomes extremely slow and alternates between running and stuck states.

Measured behavior:
- Lightroom CPU usage repeatedly reached 114–392%, with a measured spike of 755.7%.
- Physical memory footprint reached 33.3 GB, with a peak of 45.6 GB.
- System swap usage reached 30.5 GB out of 31 GB.
- vmmap showed approximately 28.4 GB allocated in Lightroom’s default malloc zone, with 27.3 GB swapped out.
- The process sample showed multiple NuPreviewProviderTasksWorker.lua queues and Camera Raw threads named InterpolateBayer, RenderIncremental_B, and GPUImageView background queue.
- The SQLite page cache was only approximately 58 MB, so the catalog database was not the source of the memory consumption.
- The Assisted Culling database did not change during the incident, indicating that active Assisted Culling analysis was not the cause.
- Lightroom logs also recorded “AgCachedCreateAutoMasks exception: dng_error_unknown” and repeated “attempt to compare nil with number” messages shortly before the incident.

After relaunching Lightroom:
- Memory usage returned to approximately 1.3–2.1 GB.
- CPU usage returned to approximately 2–3% while viewing the same files.
- The system began recovering swap space.
- Cloud upload could continue at low CPU usage, so synchronization alone does not appear to be the cause.

Expected result:
Camera Raw preview-rendering tasks should release their working memory after thumbnails are rendered, and Square Grid should remain responsive.

Actual result:
Memory appears to remain retained across preview-rendering tasks until Lightroom consumes more memory than the available physical RAM, causing severe swap thrashing and making the application unusable.

This appears consistent with a memory-retention or regression issue in Lightroom Desktop 9.5.1 on Apple Silicon. I have a process sample and vmmap summary available if Adobe engineering needs them, but I have not attached the raw diagnostic files because they contain local file paths.

    1 reply

    Anshul_Saini
    Community Manager
    Community Manager
    September 21, 2026

    Hi @Inspiring_Serenade5083,

    Thank you for the detailed report and measurements. The process sample, vmmap results, before/after relaunch comparison, and the fact that you separately checked the SQLite page cache and Assisted Culling activity are particularly useful.

    I don’t want to send you through general troubleshooting at this point. I’d rather preserve the conditions under which you observed this and collect a few data points for investigation.

    Could you please share the process sample and vmmap summary you mentioned? Since they contain local file paths, you’re welcome to send them to me by private message rather than posting them publicly.

    If the behavior is reproducible, could you also check two comparisons using the same folder and photos?

    • Does memory continue to accumulate if you remain in Square Grid without the Blue-label filter applied?

    • If you apply the same Blue-label filter but do not scroll through the resulting grid, does memory remain relatively stable?

    I’m particularly interested in separating memory associated with the filtered result set itself from memory accumulated as additional thumbnails/previews are requested while scrolling.

    One other detail would be useful: among those 417 Blue-labeled photos, do a significant number contain AI masks, Denoise, Lens Blur, Generative Remove, or other AI-based edits? You don’t need to remove or change those edits; just let us know whether they’re present.

    If you can reproduce the growth again, a short measurement sequence would also be useful, for example: immediately after launch, after opening the filtered Square Grid, after scrolling through approximately 50/100/200 images, and after leaving Lightroom idle for about five minutes. There’s no need to reproduce the 45 GB condition or deliberately push the system back into heavy swap.

    Please keep the original files and editing state unchanged for now. The information you’ve already collected gives us a much better starting point than resetting preferences, reinstalling, or performing other general troubleshooting.

    Thanks again for taking the time to document this so thoroughly.

    Best,
    Anshul Saini