• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
3

P: (Mac) Memory Leak when syncing files with the cloud

Explorer ,
Oct 29, 2022 Oct 29, 2022

Copy link to clipboard

Copied

Hallo zusammen,

seit der Version 12 (auch 12.01) scheint Lightroom den Programmspeicher immer weiter zu füllen, bis dieser überläuft.

 

Dabei arbeite ich nicht mal in Lightroom, sondern Lightroom läuft im Hintergrund und lädt lediglich die in der Cloud liegenden Fotos runter.

Bildschirm­foto 2022-10-30 um 06.23.04.png

 

Technische Daten:

 

Lightroom: V12.01

Computer: MacBook Pro

Chip: Apple M1

RAM: 16GB

macOS: Ventura (13.0)

Bug Fixed
TOPICS
macOS

Views

3.9K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Apr 13, 2023 Apr 13, 2023

Added missing bug report supplied by @Ian Lyons 

Status Acknowledged

Votes

Translate

Translate
74 Comments
Community Expert ,
Oct 31, 2022 Oct 31, 2022

Copy link to clipboard

Copied

quote

Hello everyone

since version 12 (also 12.01) Lightroom seems to fill the program memory until it overflows.

 

I don't even work in Lightroom, but Lightroom runs in the background and only downloads the photos in the cloud.

 

I'm not a Mac user, but it appears that your hard drive is almost full.

For your computer to work properly, there should be at least 20% free space.

What is the capacity of your hard drive? And how much free space do you have?

 

The folder that contains the Lightroom catalog can become quite large, because it also contains the Library previews.

My Lightroom folder is 37 GB, which includes a 35 GB previews folder.

I have 50,000 photos in the catalog, but they are stored on a different drive.

Votes

Translate

Translate

Report

Report
Community Expert ,
Oct 31, 2022 Oct 31, 2022

Copy link to clipboard

Copied

Also check/change where Lightroom Classic stores the incoming photos. By default that's in an obscure package inside your catalog folder, so that means Lightroom Classic is filling your hard disk even more. You can change the location in Preferences - Lightroom Sync.

 

-- Johan W. Elzenga

Votes

Translate

Translate

Report

Report
Explorer ,
Oct 31, 2022 Oct 31, 2022

Copy link to clipboard

Copied

Hallo,

 

die Festplatte ist frei. Es sind noch ca. 700GB von 1 TB verfügbar.

Beim starten liegt der genutzte RAM Speicher bei ca. 4GB.

Ohne das ich mit Lightroom arbeite (Lightroom liegt im Hintergrund und synchronisiert die letzen Fotos aus der Cloud) füllt sich der Speicher immer weiter.

Kommt die Meldung, schließe ich LR und starte LR neu.

Dann ist der Arbeitsspeicher wieder frei und LR synchronisiert die Fotos weiter.

Votes

Translate

Translate

Report

Report
Explorer ,
Oct 31, 2022 Oct 31, 2022

Copy link to clipboard

Copied

Nicht die Festplatte läuft voll, sondern der RAM. LR hat schon bis zu 96 GB RAM genutzt, nur um die Fotos zu synchronisieren. Die Fotos selbst liegen auf einem NAS. Dorthin werden sie auch synchronisiert. Auf dem NAS sind derzeit noch ca 30 von 84 TB frei.

Votes

Translate

Translate

Report

Report
Community Expert ,
Oct 31, 2022 Oct 31, 2022

Copy link to clipboard

Copied

Right. There have been reports about a memory leak, especially on M1 machines. I have not experienced this on my MacBook Pro 16" M1 MAX, but I wouldn't leave Lightroom running in the background for a very long time.

 

-- Johan W. Elzenga

Votes

Translate

Translate

Report

Report
Explorer ,
Oct 31, 2022 Oct 31, 2022

Copy link to clipboard

Copied

Wobei lange würde ich es nicht nennen. Lightroom schafft es unter einer Stunde den Speicher so zu füllen.

Ich denke ein Bug. Mit der letzten Version vor der 12, konnte ich LR Tage lang am M1 problemlos offenlassen.

Votes

Translate

Translate

Report

Report
Community Expert ,
Nov 01, 2022 Nov 01, 2022

Copy link to clipboard

Copied

A memory leak is indeed a bug...

 

-- Johan W. Elzenga

Votes

Translate

Translate

Report

Report
Community Expert ,
Nov 01, 2022 Nov 01, 2022

Copy link to clipboard

Copied

Please post your 'System Info' to the forum. You can access the info from the LrC Help menu. I have attached an example of what I'm requesting below.

 

System Info.png

Votes

Translate

Translate

Report

Report
Explorer ,
Nov 01, 2022 Nov 01, 2022

Copy link to clipboard

Copied

Bildschirm­foto 2022-11-01 um 18.14.33.png

Votes

Translate

Translate

Report

Report
Community Expert ,
Nov 01, 2022 Nov 01, 2022

Copy link to clipboard

Copied

I see three processes that do not take a lot of memory themselves, but could be involved because they do interact with Lightroom Classic, I believe. These are Loupedeck, exire-search and Logi Options Deamon. It might be worth checking out what happens if you disable these services.

 

-- Johan W. Elzenga

Votes

Translate

Translate

Report

Report
Explorer ,
Nov 01, 2022 Nov 01, 2022

Copy link to clipboard

Copied

Was ich noch rausgefunden habe, ist das Lightroom Classic ohne Synchronisierung auch über längere Zeit läuft.

Der Speicher füllt sich innerhalb von ein paar Minuten, wenn Lightroom Classic die Fotos aus der Cloud lädt.

Ich habe das ganze Mal ohne die Plugins getestet. Das gleiche Ergebnis.

Bildschirm­foto 2022-11-01 um 18.57.39.png

 

Die Synchronisierung nutze ich sehr viel. Ich lade die Fotos nicht direkt in LrC, sondern entweder mit Lightroom (also die Cloud Version auf dem Mac, Win PC, iPad oder Android Smartphone) oder über die Kamera direkt über das Canon Image Gateway an die Adobe CC in LR.

 

LrC lädt sie dann beim nächsten Start auf das NAS.

Votes

Translate

Translate

Report

Report
New Here ,
Nov 22, 2022 Nov 22, 2022

Copy link to clipboard

Copied

Habe aktuell das selbe Problem. Letzte Woche lief es noch ohne Probleme.

Gibt es schon Lösungen?

iMac M1

16GB

2TB

Genug Speicherplatz vorhanden, beim Synchronisieren läuft der RAM und der SWAP Voll, bis bei 50GB die Meldung kommt.

Votes

Translate

Translate

Report

Report
Explorer ,
Nov 22, 2022 Nov 22, 2022

Copy link to clipboard

Copied

Hallo, leider bis jetzt noch nicht.

Votes

Translate

Translate

Report

Report
New Here ,
Dec 14, 2022 Dec 14, 2022

Copy link to clipboard

Copied

Apologies since I know it's farily difficult to debug from little information like this, but I think there is a memory leak in the latest Lightroom versions for Apple Silicon. After keeping the app open for awhile and going through my catelog, I notice the app gets extremely slow and starts to hitch really bad. Switching between pictures is a crawl and I'll occasionally see some visual artifacts while pictures try to load in. I've seen peak memory usage in excess of 16GB while when I first open the app, usage is only in the range of 6-8GB.
Let me know if there's any information I can provide to help reproduce the issue or retrieve logs.

Votes

Translate

Translate

Report

Report
Community Expert ,
Dec 14, 2022 Dec 14, 2022

Copy link to clipboard

Copied

The best thing you can provide at this point is your 'System Info'. You can obtain same from the LrC Help > System Info menu item.

 

Note that there's a Copy button at top right corner of the System Info panel. Press this , then paste the info into your next forum post. Also, note that your post may not appear for a while as the forum spam filters may kick in. So, best not trying to repost.

Votes

Translate

Translate

Report

Report
New Here ,
Dec 14, 2022 Dec 14, 2022

Copy link to clipboard

Copied

Sure thing, here's my system info:

Lightroom Classic version: 12.1 [ 202212072312-d7ab524b ]
License: Creative Cloud
Language setting: en-US
Operating system: Mac OS 13
Version: 13.0.1 [22A400]
Application architecture: arm64
Logical processor count: 10
Processor speed: NA
SqLite Version: 3.36.0
Built-in memory: 32,768.0 MB
Real memory available to Lightroom: 32,768.0 MB
Real memory used by Lightroom: 3,567.9 MB (10.8%)
Virtual memory used by Lightroom: 412,659.0 MB
Memory cache size: 288.9MB
Internal Camera Raw version: 15.1 [ 1329 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2
Camera Raw virtual memory: 1013MB / 16383MB (6%)
Camera Raw real memory: 1046MB / 32768MB (3%)
Standard Preview Size: 5120 pixels
Displays: 1) 3024x1964, 2) 5120x2880

Graphics Processor Info: 
Metal: Apple M1 Max
Init State: GPU for Export supported by default
User Preference: Auto

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Users/evanlissoos/Pictures/Lightroom/Lightroom Catalog-v12.lrcat
Settings Folder: /Users/evanlissoos/Library/Application Support/Adobe/Lightroom

Installed Plugins: 
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) DxO PureRAW 2
4) DxO PureRAW 2 Importer
5) Flickr
6) LRT Export 5
7) Nikon Tether Plugin

Config.lua flags: None

Votes

Translate

Translate

Report

Report
Community Expert ,
Dec 14, 2022 Dec 14, 2022

Copy link to clipboard

Copied

I forgot to ask which model of Mac you're using. Based on the GPU I'm thinking it's either a MacBook Pro M1 Max or the Mac Studio M1 Max. Also,

 

- what displays have you got connected and what resolution have you them set at?

- what size of SSD and how full is it?

 

Note that increasing as you loupe through or edit images in the Develop module is expected due to caching.  However, the slow down and screen artifacts suggest something untoward is going on.

 

Can you also upload a screenshot of the 'Activity Monitor > Memory' tab (i.e. the full tab including the Pressure graphs and associated tables) when slow down occurs.  This will let us know if memory use is climbing to the point that swap is kicking in along with how much. A short description of what you were doing at the time LrC would also be helpful.

 

Apologies for so many questions, but sooner or later you're going to get above and bunch more from others on the forum. So, best get the worst of them out of the way now.

Votes

Translate

Translate

Report

Report
Community Expert ,
Dec 14, 2022 Dec 14, 2022

Copy link to clipboard

Copied

Also keep in mind that in macOS, the exact memory numbers are not that useful because of how memory is managed. As memory demands grow, the system and applications can use real memory, compressed memory, or swap memory (using storage as working memory). A low amount of free real memory is not necessarily a problem on its own because if the system can meet demands by compressing or swapping, things are still fine. Which is why Activity Monitor does not even list free memory.

 

The most useful indicator of memory usage is Memory Pressure, which looks at the total memory situation across all available resources. If Memory Pressure is green in Activity Monitor (or a low percentage in another utility such as iStat Menus), things are fine with working memory no matter what any individual memory number says; and if it’s orange or red, the memory management system has run out of ways to meet memory demands.

 

For example, if Lightroom Classic is slow and Memory Pressure is green, low memory is not the problem so you should then look at other performance metrics in Activity Monitor such as CPU and GPU usage. In this example it could be that Lightroom Classic is using a lot of CPU for whatever reason, or even that another process is using a lot of CPU and starving Lightroom Classic. But if Lightroom Classic is slow and Memory Pressure is orange or red, then you look in Activity Monitor for which applications are using the most memory and if Lightroom Classic is using way more than others then there might be possible to make a case that it’s a Lightroom Classic memory leak.

Votes

Translate

Translate

Report

Report
New Here ,
Dec 14, 2022 Dec 14, 2022

Copy link to clipboard

Copied

This is a 14" MacBook Pro with a 2 TB SSD and +500GB free.

 

I was able to reproduce it today but forgot to take a screen grab, I'll try in the near future. The reproduction was just going through photos in the catalog sequentially, going into develop for one of them and doing some edits, moving around, editing more, etc. Eventually I saw the memory pressure quite high and that's when it got really sluggish just trying to move from file to file in Library.

Votes

Translate

Translate

Report

Report
New Here ,
Dec 14, 2022 Dec 14, 2022

Copy link to clipboard

Copied

Yea the reason I believe it's a memory leak is because the performance issues are inconsistent and only arise after the application has been up for awhile. A quick reset fixes the performance hitches. 

 

Here's a mild example, the yellow region is in Develop making modifications to an image, but then even after I exit back to Library, I'm not seeing memory pressure fully recover and swap is still being used.Screenshot 2022-12-14 at 7.12.44 PM.png

Votes

Translate

Translate

Report

Report
Community Expert ,
Dec 15, 2022 Dec 15, 2022

Copy link to clipboard

Copied

There's nothing standing out as a problem in your Activity Monitor screenshot. Typicaly, if an app has been running for a while, then a memory leak will usually manifest itself in more memory being used than is pyhsically installed, which is far from what we see in your screenshot. Also, memory pressure in yellow with LrC isn't anything to be concerned about as it's more of a warning that memory use is getting tight, hence swap being triggered. In your case the pressure has dropped back into the green zone, which isn't what would happen if memory was leaking. The swap indicator will only return to zero after restarting your computer, but will reduce to a few tens or hundred MB if/when LrC is closed.  I've attached a couple of screenshots from my 16 inch MacBook Pro M1 Pro in clamshell mode with LrC running on a 4K display set to 2560 by 1440 px. Configured this way, LrC will use a lot more memory than it would if the external display wasn't used,  and it will run like a pig. Memory use and performance will be even worse if both displays (i.e. MPB display + external 4K) are being used by LrC. (Note that I had only applied a sky mask and 10 or so AI heals to two images before swap linked in).

 

FWIW, I find that a two display setup, especially if one in is a 4K configured for non-integer scaling (i.e. any mode other than 1920 by 1080 px or native 3840 by 2160 px) will perform badly with LrC. In your case, the 4K display is configured for 2560 by 1440 px, which puts it smack bang into the poor performance band https://www.youtube.com/watch?v=kpX561_XM20 ). It also seem that the performance occurs if the secondary display is on but not used by LrC.

 

Another problem with two displays when using LrC is that only the primary display makes use of the GPU. So, Develop module edits may not appear realtime on the secondary display. I've seen instances were the delay betwen and edit being applied and appeariung on the secondary display is more than a second.

 

mbp M1 Pro.png

 

Votes

Translate

Translate

Report

Report
New Here ,
Jan 16, 2023 Jan 16, 2023

Copy link to clipboard

Copied

Das gleiche Problem aktuell auch bei mir bei mir, wenn ich größere Mengen an Bildern über Lightroom Classic mit der Adobe Cloud synchronisiere. Nach einiger Zeit meldet Mac OS, dass der Programmspeicher voll ist und Lightroom Classic reagiert nicht mehr. Die Aktivitätsanzeige zeigt dann bis zu 100 GB verwendeten Swap Speicher an.

 

Gibt es inzwischen eine Lösung?

 

Mein System:

Macbook Pro mit M1 Pro Prozessor

32 GB RAM 

Mac OS Monterey 12.6.2

Lightroom Classic 12.1

Votes

Translate

Translate

Report

Report
Explorer ,
Jan 16, 2023 Jan 16, 2023

Copy link to clipboard

Copied

Hallo Christian,

nein leider noch nicht. Mittlerweile sind bereits mehrere Updates von Lightroom Classic rausgekommen. Der Fehler besteht aber weiterhin.

Votes

Translate

Translate

Report

Report
New Here ,
Jan 16, 2023 Jan 16, 2023

Copy link to clipboard

Copied

Danke für die Info. Liest Adobe denn hier überhaupt mit? Sprich, wird an der Lösung gearbeitet?

Votes

Translate

Translate

Report

Report
New Here ,
Jan 16, 2023 Jan 16, 2023

Copy link to clipboard

Copied

Habe das gleiche Problem auf einem MacBook Pro mit Intel-Prozessor und MacBook Pro mit M1.

Votes

Translate

Translate

Report

Report