Skip to main content
johns40282744
Inspiring
Jul 24, 2026 1:11 PM UTC
Answered

Merge to HDR stalls on 15.4.1, persists after clean macOS/CC install (Tahoe 26.5.2)

Description of Issue:
Merge to HDR stalls (application unresponsive, beachball) when merging exposure-bracketed images on 15.4.1. Another user in an original 15.3 thread reported this resolved after updating to macOS Tahoe 26.5. I am on macOS Tahoe 26.5.2, a newer build, with a fresh OS install, fresh Creative Cloud install, and a brand-new catalog, and the stall still occurs on 15.4.1. This rules out the macOS-update fix reported by others for the 15.3 version of this issue.

Lightroom Classic Version Number: 15.4.1 (Help > System Info)

OS Version Number: macOS Tahoe 26.5.2

Camera Model: Sony a7r V & DJI Mavic 4 Pro

Computer Version: Mac Studio M3 Ultra

Step-by-step Reproduction Instructions:

  1. Fresh macOS install, fresh CC/LrC install, no plugins, brand-new catalog.
  2. Select a set of exposure-bracketed RAW images.
  3. Photo > Photo Merge > HDR (or Ctrl+H or Ctrl+Shift+H).
  4. Merge stalls partway through; have to quit to reset the merge process.

Expected Result: HDR Merge completes and produces the merged DNG, including but not limited to adding to a stack.

Actual Result: Lightroom Classic hangs during merge, requiring quit and restart. Disabling GPU acceleration (Preferences > Performance > Use Graphics Processor > Off) works around it but is NOT a fix.

    johns40282744
    johns40282744Correct answer
    Inspiring
    Jul 29, 2026 4:13 PM UTC

    Update: I found a workaround that's holding on my Mac Studio system.

    The setting that matters is Use GPU for Preview Generation (Preferences > Performance), not the main Use Graphics Processor option.

    What I tested:

    • Use Graphics Processor off entirely: still stalled.
    • Use Graphics Processor on, Preview Generation set to Off: 57 stacks merged clean with no stalling.
    • Use Graphics Processor on, Preview Generation set to On: stalled at 39 remaining out of 47 stacks.
    • Same 47-stack batch re-run with Preview Generation set back to Off: completed cleanly.

    So Preview Generation set to Off is what resolved it for me, confirmed on the same batch that had just failed with it enabled. Setting it explicitly to On is also not a fix, which rules out the idea that Auto by itself was the problem.

    Other notes in case they help narrow this down:

    • Stall points were inconsistent, sometimes as early as image 6, sometimes with 10 to 15 remaining.
    • Batch size is not the trigger. I've had 20-stack batches stall and a 57-stack batch complete.
    • The Create Stack checkbox made no difference either way as well.

    My system: Lightroom Classic 15.4.1, macOS Tahoe 26.5.2, Mac Studio M3 Ultra, fresh OS and Creative Cloud install, new catalog stored locally, images on an SMB share. Source files are a mix of Sony A7R V and DJI Mavic 4 Pro.

    My guess, unconfirmed, is GPU resource contention between background preview generation and the merge process, which would explain the random stall points.

    7 replies

    Participating Frequently
    Oct 22, 2026 1:46 PM UTC

    After two years of batch HDR merges randomly stalling, I finally tracked down the cause, so here is what I found in case it helps anyone else.

    Setup: Lightroom Classic 15.6, macOS 27.0.1, Mac Studio M2 Ultra, 64 GB. Canon CR3 brackets, three exposures per stack.

    Symptom: Headless batch merge (Ctrl+Shift+H) of 9 to 33 stacks creates the first DNG, sometimes a few more, then the progress indicator stops at "Performing merge" forever. CPU drops to under 1%, nothing is read from or written to disk. After canceling, a new batch sits at 0% and never starts. Only restarting Lightroom helps, and the next batch stalls again. The problem has persisted since roughly Lightroom Classic 13.

    Ruled out (the batch stalled with every one of these changed): all plug-ins disabled, cloud sync paused, GPU for preview generation off and on, GPU for image processing forced on, face detection off, automatic XMP writing off, address lookup off, a brand-new catalog with 9 stacks, source files on the internal SSD instead of the external one.

    What fixed it: resetting preferences. With default preferences, the same test catalog merged 9 stacks in 100 seconds, twice in a row. I then restored my full original preferences and changed one key only, useGPUInLibrary, from on to off. The batch completed again. Help > System Info shows this setting as "Enable HDR in Library". With it on, the batch stalled every time, even in a clean catalog with no plug-ins.

    In my main catalog that alone was not enough. The second trigger turned out to be the catalog setting Assisted Culling > "Analyze photos of selected source when Assisted Culling Panel is open". I bisected the Metadata tab of Catalog Settings: with automatic XMP writing, address lookup, and face detection back on and only this Assisted Culling option off, a 33-stack batch completed. With it on, batches stalled after the first merge.

    Workaround: turn off HDR display for the Library module (confirm with Help > System Info, "Enable HDR in Library: OFF") and turn off the Assisted Culling analysis in Catalog Settings > Metadata. Develop editing and export of HDR images are not affected.

    One more observation: even with both options off, a batch started right after deleting 33 DNGs stalled on the first merge. The deletion had triggered an automatic XMP write that took 2 minutes 40 seconds, and the merge started in the middle of it. After the XMP job finished, the merge never resumed. So the underlying bug looks like a lost wake-up: a merge task that waits for catalog access while a long background write is running never gets rescheduled. The two options above just remove the most common long background jobs. As a rule, I now start batch merges only when the progress indicator in the top left is idle, and that has been reliable so far (33-stack batch completed after waiting about 8 minutes after launch).

    Reproduction for Adobe: new catalog, 9 bracketed stacks, Enable HDR in Library on, select the stacks, Ctrl+Shift+H. The merge stops after the first DNG. With the setting off, the same batch completes. In an existing catalog, the Assisted Culling analysis option causes the same stall.

    Translate
    Participating Frequently
    Oct 27, 2026 2:22 PM UTC

    Thanks for all your work on this. I’ve been using Version 15.6 and it had been stalling periodically before implementing your suggestions. I haven’t had any uninterrupted batch merges stall since using your suggestion and I’ve done a lot of large batches. I did have one single merge stall on me that I did outside of a batch while doing other work on Lightroom but it does seem to have something to do with background jobs. Thanks again for your work. It was very frustrating to me and glad to have found a solution

     

    Translate
    johns40282744
    johns40282744AuthorCorrect answer
    Inspiring
    Jul 29, 2026 4:13 PM UTC

    Update: I found a workaround that's holding on my Mac Studio system.

    The setting that matters is Use GPU for Preview Generation (Preferences > Performance), not the main Use Graphics Processor option.

    What I tested:

    • Use Graphics Processor off entirely: still stalled.
    • Use Graphics Processor on, Preview Generation set to Off: 57 stacks merged clean with no stalling.
    • Use Graphics Processor on, Preview Generation set to On: stalled at 39 remaining out of 47 stacks.
    • Same 47-stack batch re-run with Preview Generation set back to Off: completed cleanly.

    So Preview Generation set to Off is what resolved it for me, confirmed on the same batch that had just failed with it enabled. Setting it explicitly to On is also not a fix, which rules out the idea that Auto by itself was the problem.

    Other notes in case they help narrow this down:

    • Stall points were inconsistent, sometimes as early as image 6, sometimes with 10 to 15 remaining.
    • Batch size is not the trigger. I've had 20-stack batches stall and a 57-stack batch complete.
    • The Create Stack checkbox made no difference either way as well.

    My system: Lightroom Classic 15.4.1, macOS Tahoe 26.5.2, Mac Studio M3 Ultra, fresh OS and Creative Cloud install, new catalog stored locally, images on an SMB share. Source files are a mix of Sony A7R V and DJI Mavic 4 Pro.

    My guess, unconfirmed, is GPU resource contention between background preview generation and the merge process, which would explain the random stall points.

    Translate
    JohanElzenga
    Community Expert
    Community Expert
    Jul 24, 2026 3:59 PM UTC

    How many brackets do you use? I have no problems merging three A7R V files to HDR on my MBP M1 Max, Lightroom Classic 15.4.1 and MacOS Tahoe 26.5.2.

    Translate
    -- Johan W. Elzenga
    johns40282744
    Inspiring
    Jul 24, 2026 4:03 PM UTC

    It is three or five depending on the project. However, I think it is more of a case of a GPU incompatibility than a direct software relationship. I don’t have issues merging one or two at a time. When I try to batch 30+ merges at a time, that’s when it stalls. 

    Translate
    JohanElzenga
    Community Expert
    Community Expert
    Jul 24, 2026 4:09 PM UTC

    That is of course an entirely different problem than you reported in your original message! Your initial message suggests it already happens with a single merge. You nowhere mention the word ‘batch’.

    Translate
    -- Johan W. Elzenga