Skip to main content
mmarsbarr
mmarsbarr
Participant
March 22, 2025
Question

Graphics Glitches on MacOS Sequoia 15.3.2 (24D81)

  • March 22, 2025
  • 1 reply
  • 480 views

Issue: Graphics glitches whilst using LR in develop and library whilst Full Graphics Acceleration is enabled.

Step 1 Goto Performance > Enable 'Use GPU for image processing (Process version 5 or higher)'.

Step 2 Navigate the Library and start editing pictures and graphics glitches begin to apppear.

 

Expected result: No graphics glitches

Actual result: Glitches appear within the edited file but also randomly in various elements of the LR interface, sometimes even in the menu bar of the OS. Sometimes the system will crash, reboot and log back in with a crash report ready to send to Apple.

 

A WORK AROUND is to ENABLE 'Use GPU for Display' but DISABLE 'Use GPU for image processing (Process version 5 or higher)', no more graphics glitches and LRC can be used to edit images without any issues.

 

Apple Silicon M3 Max

Lightroom Classic version: 14.2 [ 202502071718-3869eef7 ]
License: Creative Cloud
Language setting: en-AU
Operating system: Mac OS 15
Version: 15.3.2 [24D81]
Application architecture: arm64
Logical processor count: 16
Processor speed: NA
SqLite Version: 3.36.0
Power Source: Battery, 41%
Built-in memory: 65,536.0 MB
Dedicated GPU memory used by Lightroom: 6,202.3MB / 49,152.0MB (12%)
Real memory available to Lightroom: 65,536.0 MB
Real memory used by Lightroom: 9,033.9 MB (13.7%)
Virtual memory used by Lightroom: 425,751.6 MB
Memory cache size: 1,641.4MB
Internal Camera Raw version: 17.2 [ 2155 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2
Camera Raw virtual memory: 3930MB / 32767MB (11%)
Camera Raw real memory: 4420MB / 65536MB (6%)

Cache1:
Final1- RAM:429.0MB, VRAM:1,930.0MB, MPR11877.CR3
Final2- RAM:189.0MB, VRAM:0.0MB, MPR11635.CR3
NT- RAM:618.0MB, VRAM:1,930.0MB, Combined:2,548.0MB

Cache2:
m:1,641.4MB, n:1,180.3MB

U-main: 143.0MB

Standard Preview Size: 3456 pixels
Displays: 1) 3456x2234

Graphics Processor Info:
Metal: Apple M3 Max
Init State: GPU for Export supported by default
User Preference: GPU for Display Enabled
Enable HDR in Library: ON

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Users/mark/Pictures/Lightroom/2025_F1_AUS/2025_F1_AUS.lrcat
Settings Folder: /Users/mark/Library/Application Support/Adobe/Lightroom

Installed Plugins:
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Flickr
4) Photo Upload
5) SmugMug
6) Snitch Sync

 

 

 

1 reply

GoldingD
GoldingD
Legend
March 22, 2025

It might be better to see full screen captures, would desire to see Histogram as well as Navigation panel, won't hurt to see filmstrip, and always show menu bar (in this case it does appear both are in develop, but..)

 

A combination of a odd Navigation panel and a odd Histogram, could point to a LrC preference file corruption, ! or ? marks in preview cells could point to file structure issues. Lack of the words Original image in the Histogram (and perhaps Smart Preview instead) could point to file issues. Wired looking filmstrip previews like that Navigation panel preview could indicate Library preview file corruption (loupe view in Develop something else), etc.

 

Likely a GPU hardware or GPU driver issue.

 

mmarsbarr
mmarsbarrAuthor
Participant
March 22, 2025

A combination of a odd Navigation panel and a odd Histogram, could point to a LrC preference file corruption.

It's not this because I tested reloading my Mac with a fresh install and it still occurs. 

 

marks in preview cells could point to file structure issues. Lack of the words Original image in the Histogram (and perhaps Smart Preview instead) could point to file issues.

It's not a corrupt file because when using the workaround as mentioned in my original post, the file is fine and can be read by numerous other programs correctly.

 

Wired looking filmstrip previews like that Navigation panel preview could indicate Library preview file corruption (loupe view in Develop something else), etc.

It cannot be this because again if I run LR without graphics acceleration it works fine.

 

The issue has something to do with enabling graphics acceleration and doing a google search it seems this issue is still prevalent with later versions of both MacOS and LR not being able to address it thus far.

 

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices