Lightroom Classic: Slow UI when using Mac and Custom Display Profile

@Rikk If you need any custom profiles for Eizo Monitors from Eizo Colornavigator please contact me.

Sorry for the misunderstanding. The profiles from colornavigator cause this problem. my post was an answer to the post above:
"Members of the engineering team may be contacting you for additional information and perhaps copies of custom display profiles."

Sorry that was my fault for not looking first at what you were replying about. So far I am thinking that enabling the GPU causes something with these custom profiles. It would be nice if more people tested this slow down with GPU disabled and then enabled to see what difference can be found. Maybe a memory issue with custom profiles and GPU enabled.

Thanks @chico11 .  If engineering requests additional profiles I will reach out to you.

@Rikk Hi Rick, we are having the same problem as everyone else but I didn’t want to add our details as we are using a 2019 Mac but with only 8GB RAM and I knew everyone would say it wasn’t enough.  However, before the update it was working perfectly.  The point is, I did as you suggested and reverted back to v.9.4 but somehow I have lost all the images!!  What did I do wrong??  Any ideas would be greatly appreciated.  Thank you.

It sounds like you opened the incorrect catalog.  You need to search your computer for files ending in .LRCAT and review the recent files until you find your working catalog. 

@Rikk

Hello Rikk, I have the same super slowness issue with an MacPro 2019 + Radeon Pro 580X_8GB and the Apple XDR 6k Display. If I use my DELL Monitor 34-Zoll (3440 x 1440) it's incredible fast. 
Then I tried resXtreme to lower the resolution on the XDR-Display just to FullHD, there is no change in performance. 
Only when I switch to the Apple color profile "Internet & Web (sRGB) and the full 6k resolution, the performance "normal-slow" is back (like before the LR10 update).
Please resolve this issue soon. If needed you can contact me.
Thank you in advance.

Regards
Ronald

This update has been terrible it’s slowed down my processing time badly.  I’m NOT happy . I hope you’re on with fixing the problem.  :( :( 

Has anyone had problems with the cloning tool?!?! It is also painfully slowwww. Ugghh!!!!

Yes, same here soooooo sloooooowwwwww

Switched the color profile to Adobe RGB on both my NEC monitors from icc profiles calibrated with Spectraview II (sRGB? Not even going there).

At least the scrolling performance in Library module has improved, but the same amount of lag when selecting particular image(s). 

Mine is a dual monitor setup, the main is a 4K monitor - NEC PA322UHD - where the main window resides. The second monitor - NECLCD2690WUXi2 - displays secondary display, grid view 99% of the time in both library and develop modules.

Develop module has been relatively unaffected. Dual screen display enables me to keep the grid view open and perform some Library functions that way but switching from one image to another is frustratingly laggy.

In my time owning 2009 Mac Pro that has been upgraded incrementally up to almost its maximum performance capability over the years to keep up with software requirements (and it is still well above the LR hardware requirements), I have never seen so many spinning beachballs - not just in LR but in any software and their applications.

cMP 5.1 running on Mojave 10.14.6

2 x 3.46GHz 6-core Xeon

64GB 1333MHz DDR3 RAM

Radeon RX 580 8GB

Lightroom catalogs are on NVMe in slot 2

Mine is a dual monitor setup, the main is a 4K monitor - NEC PA322UHD

If you unhook the 4K and do nothing more, any difference?

Yes, like night and day. I did not bother to physically disconnect but just turned off the 4K monitor and restarted Lightroom (not even a reboot).

Unfortunately, the other monitor is rotated 90 degrees to portrait orientation due to space constraints and basically unworkable without modifying the entire panel. While workspace is still roughly equivalent to that on a 15" laptop screen, the resolution is much lower and I'm working from 1 meter away.  Not a practical solution.

On the other hand, we were able to isolate at least one factor that is hindering the performance - thanks for the suggestion.

Well that's now to be expected (4K being part of the issue). Good to know. Adobe's on top of this, I suspect they have enough info to get it resolved but what we (and of course they) know is that the profile and type of display are part of the cause. 

I wonder if when drives a 4K display at less that this resolution, that clears up the problem? 

I just tried that, too (turning off one of my 2560x1600 displays). It doesn't make a difference at all in my case. Interesting, isn't it?

What does make a difference in grid view usability on my setup is minimizing the thumbnail size and turning off extras and badges (View > Grid View Style...). Still far from ideal, but definitely better...

My second monitor is a BENQ SW271 3840x2160 and I definitely have problems with that, even when mirroring my MBP 15" 2880 pixel display

I have the same problem. Somehow Lightroom slows down my entire Mac Pro 2019. Even other apps are unusable. As soon as you quit Lightroom, everything is back to speed. 

Lightroom Classic runs very slow under specific scenarios on my 16 core Mac Pro 2019, 192GB RAM, 2TB SSD with Radeon Pro Vega II 32GB GPU Card. I have an Eizo CG319X (4K) and NEC PA322UDD (4K) monitor, however LrC is set to only use the Eizo.  Specifically, I noticed two major issues since upgrading to Big Sur and LR10.0 (same issues persist in 10.1):

When in Library module, if I zoom an image to 100%, trying to pan the image is jerky and slow.  Panning the same zoomed image in develop module works smoothly as expected.  PS: Hardware GPU acceleration is set to auto.  Changing to sRGB profile makes no difference.

The second issue I have is that within 5 minutes of viewing photos, adding some adjustments like spot removal, my GPU RAM usage jumps from about 2GB to 32GB, which then causes the Apple WindowServer process to consume large amount of CPU and my whole machine becomes extremely slow and jerky.  Closing Lightroom immediately causes the RAM usage on the GPU card to drop to standard levels (2-4GB) and the performance returns to normal.

In fact, with Lightroom closed right now my GPU RAM usage is 5.7GB.  I launch Lightroom Classic, GPU RAM usage is still 5.7GB.  I open the develop module, it jumps to 9.92GB.  I then take the heal spot edit tool, use 75, 75, 100 brush and click on a photo (Sony A7R4).  GPU RAM usage jumps to 12.48GB.  Add another spot, it jumps to 14.7GB.  Add 17 more spot corrections, and my GPU usage is 100% - all 32 GB of VRAM is used.  WindowServer starts running up to 40 - 80% CPU and everything slows down.

Close Lightroom, GPU RAM usage drops to 1.9GB.

You are in the same boat as me. I can't use 10 so I am using 9.4. Question do you need to use 10 or is what you need on 9.4?

In about two week I will have MP2019 to test 10 on a clean install. I will install LR10 first and see what happens as I install the rest of the software. I am inclined to think that there is some other conflict somewhere, because I shared my custom profile with someone here. On his machine neither custom profile caused a problem and on my machine both custom profiles caused the problem.

I can use 9.4 but I did a lot of work since so downgrading means I lose a lot of work and new images that I will need to reimport / index / keyword / etc.

I will also be getting a MacBook Air M1 in early Jan and will test a clean install of Big Sur + LR10.1.

"reimport / index / keyword / etc" Are you only saving this in the catalog files and not in the DNG or XMP files?

No, it is set to write to XMP but I do not always trust that as I had conflicts in the past.  Also, all files imported since will need to be re-imported because they are in the new catalogue but not the old.  They come from various sources.

@Rikk First of all, thanks for steering me in the right direction.  I dropped from LR10.1 to 10.0 and the problems went away.  Here's some additional details that I learned through repeated attempts to diagnose that might help the coders at Adobe to straighten this out. 1.)  The problem on appeared on my iMac with 27" Retina display.  It did not appear on my MacBook Pro.  Both were running LR 10.1 and Big Sur 11.1.  2.)  I was able to determine that the problem was the cursor display point on the iMac, specifically when the cursor was providing input such as moving a slider, changing the size of the crop box, etc.  The cursor indicator on the screen would stop moving, but it appeared the system was still recognizing the position of the trackpad or mouse.  (I tried both.)  When the cursor indicator briefly unfroze it would jump to a new position where the input had been, and then freeze again.  Hope that helps.

@Rikk Adobe RGB and sRGB monitor profiles do not fix the problem for me. What else could this be?

2013 Mac Pro, Dual AMD D700 Firepro, multiple NVME SSDs, LG 27" 4k display.

@ Rikk 

Hello Rikk,

I have changed the monitor setting to both sRGB and AdobeRGB. Both did not bring success. If I move the slider of e.g. Dynamic several times from right to left it suddenly hangs. It takes more seconds until the program reacts again. From this point on, lightroom reacts only very slowly. Also, the preview is no longer displayed correctly. In my last attempt, the edited image was displayed with a green bar that took up about a quarter of the image. I can also send you the lightroom system information text file.

It sounds like your issue is unrelated to this thread. Have you started a fresh thread with your system information?

@rikk I received the following message from Victoria Bampton:  "I've merged your reply into the original post. To reply, use the Comment on this post here... box at the bottom of the page rather than starting a new thread."

I must have accidentally started a new thread. Do you want my system information?

If you system is behaving as described in the Official Post on this thread, no need to start a new thread or provide any information. 

If you system behaves differently, then you should start a new thread with complete information.

Review the official post on Page 1 to determine how to proceed. 

@Rikk With respect, this is two months old, and the issue is still not resolved. LR 10 is simply not ready for professional work. Adobe should not have released it.

@Rikk that's great advice, except it does not work, as LR 9.x does not recognize the v10 catalog. 

Not to mention, any of LR versions recognize my external GPU, which is a different story :D

Mac Pro 2013

3.5 GHz 6-core Xeon E5

32GB RAM

AMD FirePro D700 Dual (internal)
AMD Radeon Pro Vega 64 (external)

@Rikk Hi, having issues after updating. Details of my system

OS: Big Sur 11.1
MacBook Pro (Retina, 15-inch, Mid 2015)
Processor: 2.5 GHz Quad-Core Intel Core i7
Memory: 16 GB 1600 MHz DDR3
Graphics:
AMD Radeon R9 M370X 2 GB, Intel Iris Pro 1536 MB

Have tried changing the to ADOBE RGB and still having issues.

Cheers

@Rikk  Exactly my issue - 28"Samsung 4k monitor calibrated by i1 Profiler. Painfully slow - 2-3 sec to render each photo using custom profile, move Lightroom over to 2nd 1080p monitor and photos render immediately - even though it also has a custom calibration profile. Switching the 4k to sRGB speeds things up greatly, but not as fast as the 1080p - expected. Opening LR in low-res mode also helps even with custom profile.

OSX 10.14.6 with i7-3770, 16GB RAM, AMD RX580 8GB, photo library on external SSD through USB3. Internal drive also SSD on SATA6 bus.

@Rikk 

Have the engineers check the MEMORY LEEK.

I think it's a MEMORY ONION or maybe memory shallots <g>.

The engineers have checked all kinds of attributes. 

If you cut the Memory Leeks into small pieces, (called bytes) and add them with eggy-weggs, salt and pepper to a heat sink, you can have a delicious geek breakfast (while waiting for a fix!)

@carlos_cardona I cut them into bits and they did not byte...No as tasty I guess :)

@Rikk Count me in here too, but downgrading isn't an option because of the 16" mbp performance problems in the older version (though it would also fix the slideshow bug in the other thread).

Color managed workflow is critical, so I guess we're stuck?  I'm rather surprised that this made it through QA without being caught.

@Rikk I have the same issue on my Mac Pro with a custom color profile. Switched to a provided sRGB profile and performance is adequate again.

System:

- Mac Pro 5,1, 2x 6-Core 3.46GHz X5690 Processor

- Radeon RX580, 8GB

- 40GB RAM

- All data on NVME and fast SSD

- Mac OS Mojave, latest Lightroom

Let me know if I can help by providing more information or profiles.

Welcome to the club! Who will draft the charter? It’s about time after four months... ;)

I opened lightroom today after deleting a number of files last night and bang zipped along, for about 3 photos and then steady degradation affecting the whole computer. Photoshop won't even open. Stuff popping up making me go what??? It's as if all the commands are spaghetti. Finally computer froze and had to shut off and turn back on. Not Acceptable. Imac running Catalina, 16 GB ram. 

Here is my card - The Radeon Pro Vega 56 is a professional mobile graphics chip by AMD, launched in August 2017. ... AMD has paired 8 GB HBM2 memory with the Radeon Pro Vega 56, which are connected using a 2048-bit memory interface.

The Vega 56 is on Apple's maybe list. "Metal" support is required for Lightroom to make use of the card. 

The following cards are known to be Metal-compatible: 

MSI Gaming Radeon RX 560 128-bit 4GB GDRR5
SAPPHIRE Radeon PULSE RX 580 8GB GDDR5
SAPPHIRE Radeon HD 7950 Mac Edition
NVIDIA Quadro K5000 for Mac
NVIDIA GeForce GTX 680 Mac Edition

 
Apple also lists cards that "might also be compatible" with macOS Mojave: 

AMD Radeon RX 560
AMD Radeon RX 570
AMD Radeon RX 580
AMD Radeon Pro WX 7100
AMD Radeon RX Vega 56
AMD Radeon RX Vega 64
AMD Radeon Pro WX 9100
AMD Radeon Frontier Edition

@bill_3305731 6GB of VRAM isn't enough to scroll some content in a window? Come on… Especially since it worked nicely in the previous version and every other application - including other Adobe ones.

I appears that your video card is unsupported. Technological progress I guess. 

On Windows with both 4GB and now 5GB Nvidia Quadro video cards (4K monitor), scrolling was fine but has slowed down with V10 but only a little; just enough to notice. 

In the Performance tab in Lightroom's settings, it says the the GPU is fully supported. Plus, all the actual heavy lifting editing functions work quickly as expected. And actually, now that the adjustment brush is GPU accelerated, that works like a dream as well.

It really just the UI that took a hit this update. At least on a Mac, I can see something definitely changed in the way the UI is rendered but I can't put my finger on it. The font in the Develop module's drop down lists is different. Something was definitely updated but there's clearly a bug here.

This is a good example of when Adobe would really appreciate a video recording of what you're seeing. Regarding the font, it seems like it was intentionally changed throughout the interface. Win 10 here.

Bill, you're way out of your depth here. Time to move on. 

Hi, i figured out, that with calibrated monitors on MacOS the library view in Lightroom CC v10 is round a bout 20 times slower, than with monitor profile "apple RGB" chosen. The editing section is fine and run flawlessly  with the profiles from calibrated monitors.

Here we have EIZO monitors with color navigator software on catalina. We  can reproduce this behaviour through all Macs in our whole company.

The same behaviour is in Indesign v16 and illustrator v25.  Adobe Photoshop does not have this issue... !

It does not matter if I build the profile with EIZO Color Navigator or with i1Profiler from XRite (always ICC version v2).

It is awful. we cannot use the Adobe CC anymore.

I have yet to see this problem with ID16 but here again I do not have GPU Performance selected. Will try to select it and see what happens.

Glad to read this as I noticed this slowdown on my iMac too. (I reverted to 9.2.1 though, due to the clone/heal bugs when used at the frame edges, which were introduced in 9.3).

Same Here...

MAJOR slow down in virtually every way.

@Brad Bahr

Thanks for brining to my attention the fact that you can actually downgrade.  I have gone ahead and downgraded both Lightroom and Photoshop, in which they've removed the line-arrow pixel tool for no good reason.  I've also disabled automatic updates for Lightroom.  A complete disaster.  Adobe takes our subscription money and then releases half-baked software to us like gunea pigs.   

Still requires a video card supported by Lightroom. Unfortunately Adobe has stopped listing supported video cards so for other than mid to high end Nvidia cards, it's a guessing game. The Vega 56 is a "maybe" card.

Business reality: if 1 in 10 thousand people with a computer do photo editing and maybe 1 in a thousand of them do it on a Mac with an AMD video card... You get the picture. 

Based on your experience, a change in Lightroom v10 probably pushed your card from the "maybe" category into the "unsupported" group. Adobe delivered a significant number of significant performance improvements with V10. It is likely that those improvements will be a setback for some hardware. AMD and Nvidia use significantly different APIs for communication with the card. Add in the variations from one card architecture to another within a brand and the problem becomes obvious. 

Yet here we are after spending $6000+ on computers less than 3 years old, our work is coming to a stand still. Even though Apple says they are supported and Adobe says GPU with Metal Support work. And even if they don't support, why is it slower than it was in 9.4?

I know $$$ laptops has similar performance like $ desktop. But this is a 4000$ notebook that could handle the software very nice till today when I updated it. If I was using some crap 500$ notebook I will understand it but this is a "pro" machine and if it cant handle 24mpx raw files there is some problem. And in my experience, the problem is in the software. Or we are now in a time where high-end machines are usable only for one year and then they are good only for youtube?! I also work in Premiere Pro and Davinci Resolve and I learn something there. When you have two software that can do the same thing and one can do it a lot faster than the other on the same machine you can tell that the problem isn't in hardware but in software optimization. I am downgrading LRC and wait for Adobe to FIX this.

Recent Nvidia Quadro and GeForce cards should be fine but there is always the issue with MacPro compatible drivers.

In your situation, I would contact Nvidia support though they are likely to recommend the latest cards. And check with Adobe support to see what they say about the problems you are having with your card. They might already be planning a fix. That would be free. 

Also measurements I've taken, reported in another thread, indicate that Lightroom is making much heavier use of the processor to provide performance improvements. All develop tools that I've tested are now instantaneous on my Windows Xeon 3.6/4.0 GHz machine with most of the improvements coming from heavier use of the processor. 

People who don't know how video cards work think that we would unconditionally benefit from Lightroom increasing its use of the video card. However for many functions, a video card is a bottle neck. This is especially true if the whole image won't fit on the card. Just take one unrealistic example, if Nvidia were to release a 32GB version of the P4000 and Lightroom were to require that card; we would see a speedup for most functions. But not all. 

Of course, the most straightforward solution for you is to switch to Windows, notice the flood of problems primarily by Mac users. Think what it is going to be like with a new version of Lightroom running on the totally new version of MacOS on a new hardware architecture. This forum is going to be buried with bug reports. 

@lewis_kemper 

I didn't read your question correctly, my mistake. I don't believe that Lightroom will work with an external GPU. Saw that posted somewhere but don't remember where it was. 

Can you just stop? I've read this whole thread and you've repeatedly spouted nonsense. You obviously don't know what you're talking about, but feel compelled to advise anyway.  

Please, please stick to topics that you know something about, its not helping anyone. 

Reality is painful to those who live in the the world of wishful thinking. Interesting how you can't identify a single error in my comments. 

do we really need to have flame wars here, too?  

Bill is spouting nonsense. I have a heavily upgraded MacPro 5,1 with PCIe SSD, 48GB RAM, SSD photo storage and Radeon RX Vega 56 GPU (8 GB with full boot screen EFI courtesy of MacVid Cards) and EIZO CG318-4K calibrated monitor. On LR 9 this set up is blazingly fast. On LR 10 it is a joke. If I use a standard factory profile the speed comes back but I no longer have an accurate monitor. I have reverted to LR9 for the time being. Photoshop 2021 also works blazingly fast with this card and set up. This is a bug ridden software issue and Adobe needs a kick where it hurts most - customers migrating to other, more reliable, software.

Belinda,

MacBook Pro 16, 32 GB RAM, 2TB SSD, external Dell 4K 27" monitor. 

5 catalogs upgraded from V9.4 to V10. Mostly raw images but a few thousand JPEGs as well as a few tiff and DNGs. 

Absolutely no slowdowns and only able to reproduce the Clone bug which Adobe has accepted. 

Perhaps you need to replace your Etch-A-Sketch with a real computer. 

I'm not going to get into a ya-boo equipment superiority contest with you.

If you are right, which I doubt, then Adobe should be even more ashamed of themselves. If access to Lightroom is to be limited to the very latest gear and GPUs then a large chunk of their customer base is going to evaporate. Most contributors here have excellent machines by any normal standard and it's not unreasonable to expect that faithful, subscription paying customers are extended decent support. This kind of laissez-faire attitude, displayed so often before does no one any favours except perhaps a few big heads who want a forum for chest beating.

Bill, is everything ok at home…?

And you don't find it curious that thousands of Lightroom users are not having your problems, most running on less than the latest gear. 

You need to chill out as you are not demonstrating anything but your ability to make a fool out of yourself. Why don't you chill out and read some of the threads whereby people have come up with real solutions to their problems. 

And if you want some assistance, provide some useful information such as your hardware and software configuration, whether you are using plug-ins and your specific issues. 

There are quite a few very knowledgeable folks on this forum who can probably help you out. That is, if you want some assistance and are not just looking for someplace to rant. 

Bill, is everything all right at home....?

Actually @bill_3305731, because of this post, Adobe have been very helpful. They reached out and signed me up to their beta testers program and trying the future release along with other beta testers. My video card is indeed supported and all counter arguments you made have proven to be incorrect. We are helping Adobe work through this issue. Thank you for your input.

It's good to be humbled occasionally, thanks for the feedback. 

There is a bug. It's pretty rare in that no one inside Adobe or outside within beta (myself included) ran into the bug. Bill is mostly right and of course Adobe didn't go out of it's way to release the bug. It will get fixed, everyone smart enough to back up prior to update can revert to the last version and get back to work.

No software is bug free. 

Complaints will not speed up the fix! 

With respect, without complaints there would have been no fix. And yes, bugs happen, it's just that Adobe has cornered that market for ear plugs.

“My core belief is that if you're complaining about something for more than three minutes, two minutes ago you should have done something about it.“ -Caitlin Moran

Just report issues, properly, and move aside:
https://www.adobe.com/products/wishform.html

That's a sound core belief.

Perhaps one day Adobe will adopt it.

@bill_3305731, your comment:

And you don't find it curious that thousands of Lightroom users are not having your problems, most running on less than the latest gear. 

is quite insulting

regards

Don't waste your time (like I did). The problem is in the software not in your machine. The RX580 is a great card and fully compatible. Just revert to the previous LR version (you will need your old catalogue) and carry on until Adobe sees fit to fix this cock up.

Imagine, Lightroom - designed for photographers - won't work with custom monitor profiles. It's laughable.

Belinda, I found that re-calibrating my screens fixed the speed issues. Been running 10 for weeks now.

See Belinda, there are people here who can help you when you ask instead of ranting. 

Are you saying that a simple recalibration fixes the problem? It's so easy to do with ColorNavigator on an EIZO, I will kick myself around the room for not thinking of that if you are right.

I wasted a full day messing around with every conceivable fix - except that one. I will try that tomorrow. Thanks.

Yes, at least it has worked for me. I did a bunch of testing, switching back to old calibration profiles and the only profiles that worked are AdobeRGB 1998, and sRGB, and then any new profiles since v10 was released.

A recalibration did NOT work for me... I think it is hit or miss.....

It covers all the bases:

• for some it does nothing
• for some it makes it worse
• for the lucky ones it fixes it, not many of them have reported here
• while certainly not an option for serious work, the mostly consistent fix is to switch to the OS default sRGB and no, I'm not suggesting that

Tongue in cheek (where's a emoji when you need one), one can always switch to Windows, we are only experiencing a couple of minor problems. 

See Bill, there was no ranting here - other than you on your high horse belittling those with lesser equipment than yours and spouting opinionated nonsense.

Now go munch down some of that humble pie. Yum.

Not too much tongue in cheek Bill, I'll take the Macs far, far fewer GPU issues that so often crop up on Windows. 

This is a real issue and I signed onto this thread early on and would like to stay on it so that I can be aware of a fix at the earliest opportunity possible as this truly affects my workflow and productivity for my business... However some are making it difficult to stay on this thread with the petty back and forth. Can you please all take a step back, post only genuinely REALISTIC and constructive comments and stop blowing up everyone else's inbox?

Thanks and Happy Thanksgiving!

@Andrew, Belinda: it's not worth it arguing with religious extremists, don't waste your time, leave it alone. -25 years Mac IT Pro.

Carlos, thanks for the Thanksgiving Day humor. 

@davidmantripp  :-  Can you please provide more details on the slowness issues that you are facing? 

We have tried to compare apply develop presets to 1000+ images to compare the time between 9.3 and 10.0 but it almost took the same time.

Can you share the develop preset that you are applying on the images and if possible, a recorded video would be of great help.

Please share the dropbox/we transfer link and send it to mayugupt@adobe.com

Thanks for reporting. 

Mayuri

It is a problem with the profiles, not with the hardware. The image rendering in Lightroom (Library module), Indesign and illustrator also is broken. Here you have a youtube vid, which shows the mess. It is in german, but you can see exactly what i am doing and when the image rendering in lightrooms library module slows down:

I am not. Like I said above my desktop rig with 3900X, 64GB ram, RTX2070Super with latest Win 10 works great. Dont know if its due Nvidia GPU in the PC or slower HW in MBP.

Here is my Lr System info: 

Lightroom Classic version: 10.0 [ 202010011851-ef6045e0 ]
License: Creative Cloud
Language setting: en-US
Operating system: Mac OS 10
Version: 10.15.7 [19H2]
Application architecture: x64
Logical processor count: 16
Processor speed: 2.4 GHz
SqLite Version: 3.30.1
Built-in memory: 32,768.0 MB
Real memory available to Lightroom: 32,768.0 MB
Real memory used by Lightroom: 2,618.7 MB (7.9%)
Virtual memory used by Lightroom: 32,387.7 MB
Memory cache size: 2,251.3MB
Internal Camera Raw version: 13.0 [ 610 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 1564MB / 16383MB (9%)
Camera Raw real memory: 1632MB / 32768MB (4%)
Displays: 1) 6016x3384

Graphics Processor Info: 
Metal: AMD Radeon Pro 5500M

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Users/xxxxxxxxxx/Library/Mobile Documents/com~apple~CloudDocs/a_Lightroom/Master_Lightroom_Catalog/Master_Lightroom_Catalog-2 2-v10.lrcat
Settings Folder: /Users/xxxxxxxxxx/Library/Application Support/Adobe/Lightroom

Installed Plugins: 
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Facebook
4) Flickr
5) Nikon Tether Plugin
6) Smart Shooter 4

Config.lua flags: None

AudioDeviceIOBlockSize: 512
AudioDeviceName: $$$/dvaaudiodevice/SystemDefaultAndEffectiveDeviceName=System Default (MacBook Pro Speakers)#{comment}DVAAU-4201250: Open the audio hardware preferences page.
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: LR5x42
CoreImage: true
GL_ACCUM_ALPHA_BITS: 0
GL_ACCUM_BLUE_BITS: 0
GL_ACCUM_GREEN_BITS: 0
GL_ACCUM_RED_BITS: 0
GL_ALPHA_BITS: 8
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: AMD Radeon Pro 5500M OpenGL Engine
GL_SHADING_LANGUAGE_VERSION: 1.20
GL_STENCIL_BITS: 8
GL_VENDOR: ATI Technologies Inc.
GL_VERSION: 2.1 ATI-3.10.18
OGLEnabled: true
GL_EXTENSIONS: GL_ARB_color_buffer_float GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_seamless_cube_map GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_depth_bounds_test GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture_array GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array_bgra GL_APPLE_aux_depth_stencil GL_APPLE_client_storage GL_APPLE_element_array GL_APPLE_fence GL_APPLE_float_pixels GL_APPLE_flush_buffer_range GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_packed_pixels GL_APPLE_pixel_buffer GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_specular_vector GL_APPLE_texture_range GL_APPLE_transform_hint GL_APPLE_vertex_array_object GL_APPLE_vertex_array_range GL_APPLE_vertex_point_size GL_APPLE_vertex_program_evaluators GL_APPLE_ycbcr_422 GL_ATI_blend_equation_separate GL_ATI_blend_weighted_minmax GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_IBM_rasterpos_clip GL_NV_blend_square GL_NV_conditional_render GL_NV_depth_clamp GL_NV_fog_distance GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_barrier GL_SGI_color_matrix GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod 

I'm getting the same problem, latest OS but on a 2013 iMac (yes, I know its old but was working with Lightroom very well prior to the update.).

What was a simple task previously such as spotting out dust now beachballs for 2 or 3 minutes.

I would love to be able to recommend updating but Lightroom doesn't seem to be quite ready yet...

Can you change monitor custom profile  to "SRGB"  and share your feedback ?

Thanks

Mayuri

@Christoph Meyerdierks :Can you change monitor custom profile  to "SRGB"  and share your feedback ?

Thanks

Mayuri

@moritzfaehse :- Can you change monitor custom profile  to "SRGB"  and share your feedback ?

Thanks

Mayuri

I have the same problem.....

Mac Pro mid 2013 

RAM 64GB

Double AMD Radeon D300 3GB

The problem star when I use Texture......in LR Classic

I Must disable GPU Accel.

Your GPU lacks sufficient RAM for Lightroom V10 if your monitor is higher resolution than FHD. Only one of the cards is used by Lightroom BTW. 

No lacks...

I’ve monitored GPU RAM and GPU:

GPU RAM: 35% used only

GPU:  5-10%

I downgrade to LR 10.0 And Now work again smoothly. 
The Upgrade is the problem.