P: Slow UI when using Mac and Custom Display Profile

The point was nothing short of a massive lawsuit, or something more unspeakable, seems likely to getting their attention

Please stop, this is absurd. Please read the agreement you made with Adobe that spells this all out. Try schooling yourself on the legal agreement YOU made when you agreed to use the product. 

The point was nothing short of a massive lawsuit, or something more unspeakable, seems likely to getting their attention. They do not care. Not even a little bit, as evidenced by their complete failure to warn anyone, or provide guidance on workarounds or a timeline for a solution. 

As for the suggestion that moving my entire production and 50TB worth of data and all my other software (video, music libraries, email, etc etc) over to a PC environement, and then learning how to operate in that environment after a 15 year hiatus, with no tech support... it would take a month, minimum to get back on track. It is the single most painful choice one could make when already behind. It's basically choosing to tear down an otherwise good house instead of fixing the plumbing. 

Since I have schooled myself on the details of Adobe's 'malware', it is a less expensive, more productive path for now to keep rebooting the software to avoid crashes from Adobe's inability to manage RAM use and live without GPU acceleration and buy a new monitor with hardware calibration built in. Once caught up, it would be much, much faster to migrate to Capture One, which works faster and produces better RAW conversions than move all that data to a new $$$ PC setup... only to hope Adobe doesn't make a mess of that environment at that point. All while sending away tens of thousands of dollars in work from longstanding clients while simultaneously fending off their daily inquiries on existing projects. It's the worst possible choice. 

Adobe's handling of this problem that they have directly created has been utterly reprehensible. Full stop. 

Especially when they've known about the problems for months on end.

Nope. Not accurate and an assumption.

And no one forces you to update, not keep the backed up older catalog, not test before rushing ahead etc. 

He has a right to complain. 

The bit about a class action? That failed after he and others agreed that can't happen. 

You shouldn't have to subscribe to a forum to know whether the company you're paying is about to risk your livelihood without even telling you. Especially when they've known about the problems for months on end. Imagine if were were expected to be on car forums to know whether our tires were going to explode or our brakes were about to fail! NO, the onus is on the provider of a product or service to communicate when they cannot fulfill their end of the bargain. 

You are wasting your time Andrew, he wants to suffer. You can't help people like that. 

It's grounds for a class action lawsuit.

Read the EULA; not a chance. 

That's ridiculous. I've been using the same stable, reliable Mojave release for years now. The problem started after the Adobe LRC 10 update... and the problem exists across a variety of MAX OS versions. It wasn't a problem in LRC 9. 

Moreover, Adobe KNEW about this problem and did not send ANY notice to ANYONE about it. They let people like me download it long after the problems were known, and convert massive catalogs that couldn't be switched back, and NO NOTICE of the UTTER HELL we were entering into. 

It's grounds for a class action lawsuit. I have real damages. 

I've only come to figure out the RAM issue and the custom monitor profile issue and the GPU acceleration issue by happening upon the right discussions. NO HELP, NO NOTICE, NO FOREWARNING, NO ACKNOWLEDGMENT FROM ADOBE. Total malfeasance on their part. 

And yet you think the entirety of this is 'a result of a problem on Apple's end'. WOW. Are you paying ANY attention to ANY of this? <facepalm>

This is more likely to be an Apple problem that was partially fixed with macOS 11.2, completely solved for our iMac. Another macOS update was just released, supposedly fixed some security problems but probably some other fixes as well.

This blame game by Apple users that all apparent Lightroom bugs are caused by Adobe software is getting silly. Since the memory management code is probably identical for both the Mac and Windows versions of Lightroom and because this problem doesn't occur on Windows, it is most likely a macOS bug. 

My recommendation to the OP to switch to Windows was to keep from going out of business. The OP seems to be in dire straights and in desperate need of a solution. So he can make a switch and stay in business or be unemployed for an indeterminate amount of time while waiting for a fix. 

Bill_3305731

This discussion of Apple vs. Microsoft reminds me of MaCoys vs. Hatfields or Canon vs. Nikon. Everyone has their own preferences and there is no need for pushing one doctrine agains other.  It is not the machine problem it is the Adobe Software problem. Adobe software does not release the memory allocated to it, therefore, once the RAM memory runs out of resources it will quit. The engineers at Adobe need to fix this before the software will properly work on any machine.