Just helping to clarify what you see in the screen shot in the first post, because I’ve run into it a few times…
That is a macOS emergency warning about RAM usage specifically. The user should normally never see that warning.
It is not directly related to being out of virtual memory swap space, although running out of VM space can be a side effect.
I’ve seen this error several times over the years (the pictures below are from a few years ago), and in my opinion this is the result of a memory management bug in the application or in macOS.
In other words, I think this warning is probably not directly caused by anything the user is specifically doing wrong, and probably can’t be addressed by checking settings.
On my MacBook Pro with 32GB unified memory, I’ve seen other Adobe applications trigger this memory in the past. The screen shots below are from 2022 and 2024. In those cases I was not doing anything especially demanding, so it can be difficult to troubleshoot on the user end. This contributes to my suspicion that it could be, for example, an unanticipated memory leak in the application or the OS that needs to be fixed on that end.
For example, when Adobe Media Encoder and Premiere Pro went out of control in the picture below, I was very puzzled because I was only rendering a series of simple sequences of just cuts and maybe a fade or two, one video track and one audio track, almost the simplest editing you can do. No special effects, no large frame sizes. Same with Bridge…how complicated can you get in a file browser? But in both cases the Adobe apps were requesting many times the amount of actual RAM was on the memory chips, and 32GB is not minimal. So I figured…that’s a bug.
The point of this post is that might not be much that can be done on the user end to prevent that warning. Something is spiraling out of control in memory management that may be outside the control of the user. That’s just my opinion, of course; would be good to hear from Adobe about what might really be happening. (Yes, I submitted bug reports when these screen shots were made years ago. And I haven’t recently seen that error in those applications.)
So what can robin_2 do? I’m not sure because the problem can be so unpredictable. Aside from restarting, I see that LoupeDeck is in the application list, and that gives me the idea to maybe try disabling Lightroom Classic plug-ins (only temporarily), in case a plug-in (LoupeDeck integration?) is interacting weirdly with Lightroom Classic memory management. You can also try the same “process of elimination” test with third-party background processes running in macOS. I never figured out what caused it on my Mac, it just stopped happening after a while.