P: Slow UI when using Mac and Custom Display Profile

[adamcrowe]

Hello,

Since upgrading to Lightroom Classic v10.0, all UI-related functionality is painfully slow. All editing functions are working correctly and quickly but scrolling through the catalogue or even scrolling a side panel is taking many long seconds to refresh. Unreasonably long.

Disabling GPU Accellaration has no affect on my Lightroom's performance.

macOS Mojave 10.14.6

Mac Pro (Late 2013)

3 GHz 8-Core Intel Xeon E5

32 GB 1866 MHz DDR3

AMD FirePro D700 6 GB

[sethk60189077]

Andrew: phrases like "Adobe's lawyers would have to kill me, then you" undermine your believability.  If your information is correct, it should be coming from Adobe and makes me wonder why Adobe wouldn't be providing it. You go on to say: "posting here about it will not make the fix come any faster (kind of the opposite actually)", which suggests you really have no idea what you are talking about.  If posting about the problem makes Adobe purposely slow down the fix we have a far bigger problem.  Provide actual information or stick to your knitting.  Thanks. 

[FeedbackCommunityMember]

Andrew was making a joke, Seth! Sheesh, lighten up Homes! We can all use a little humor here, right? Remember humor? Adobe engineers don't need more stress, I think that was his point, and on that everyone can agree!

[TheDigitalDog]

Andrew was making a joke, Seth! 

Yes I was Carlos, seems unlike you, Seth missed my deliberately placed <g> and is a bit humor im-impaired. <g> 
And for Seth, one more: <g>

[thierryn48516695]

@andrew_rodney 

Hi

OK for humor, OK for NDA, even OK for "small".

But debugging is not Rocket science.

Have a computer where the bug happens
Compile with max debug level

Disable new developments one by one, or package by package
Analyse

It should take some days, not months.

The only reasonable conclusion is that this bug is absolutely not a priority for Adobe (I can understand in COVID time...)

"Hard to find" bugs is just a very romantic approach to the problem: you know what you have modified between 2 versions!!

If Adobe is able to track all modifications between V9.4 and V10, then it is very a elementary development technic.

Another possible "issue" could be Adobe has lost V9.4 sources and CVS or equivalent basis for tracking modifications. This can happen when you get serious issues at the same time on your main storage and on all you backup storage, local, and at least 2 remote storages.

If this kind of problem happened, I would be very patient and very understanding.

Kind regards
Thierry

[TheDigitalDog]

But debugging is not Rocket science.

It should take some days, not months.

Your experience and understanding the Adobe source code is exactly what sir? 

Or you're again assuming...

Again; your experience in production of this software is what?

Or you want us to believe Adobe want to have such bugs and are not taking a fix serious based on what data from Adobe? Be very specific please; no more assuming.

[kimballisms]

Reminds me of the quote:

"No job is too difficult or too expensive for the man who doesn't have to do it himself"

[TheDigitalDog]

"Hard to find" bugs is just a very romantic approach to the problem: you know what you have modified between 2 versions!!

And no ideas how the OS and enormous number of hardware differences differing users work on affect a product until you do.

I have NO SUCH bug issues today or with any build of the product: specifically tell me and Adobe why? 

You assume again, this bug is easy to find and easy to fix. Without data and experience with this issue, you're just another poster with a opinion. 

Remember that old saying about opinions? 😉

[thierryn48516695]

@andrew_rodney 

My experience is multi millions lines software developments and CMM5 software quality insurance auditor.

There are basic development principes that you just seem to ignore, that do not depend on the kind of software you develop.

If you do not understand that tracking modifications from a version to another, disabling them one by one, is a basic and simple way to track bugs, I cannot help you.

Kind regards
Thierry

[TheDigitalDog]

My experience is multi millions lines software developments and CMM5 software quality insurance auditor.

As I suspected, zero understanding of how to code for Adobe products, and their audience. Of course, your software products are utterly bug free! 

There are basic development principes that you just seem to ignore, that do not depend on the kind of software you develop.

As you've ignored the huge number of Adobe customer hardware, OS versions, 3rd party OS hacks installed, lack of updates to drivers etc. 

You've ignored that Adobe has recognized, admitted and has said they are working on a fix. 

I cannot help you.

Or Adobe. Or their customers. But if venting makes you feel better, by all means, knock yourself out. 

[thierryn48516695]

You only need ONE computer where the bug happens. So please stop talking about the huge number of possible configurations.

[thierryn48516695]

In case you do not realize, playing Adobe Advocate with void useless information and customers contempt, will hurt you, one day or another.

[sethk60189077]

Andrew:  I understand the sarcasm <g>, but what is the point?  You know these details about Adobe and the imminent "fix" because......????  You spout your credentials, belittle others, and provide no real information.  Thanks for your contributions <G>

[TheDigitalDog]

You only need ONE computer where the bug happens.

The absurd is the last refuge of a pundit without an argument.

You know these details about Adobe and the imminent "fix" because......????

I've been an Adobe beta site since 1991, I routinely (multiple times a month) meet with various team members, I communicate with other testers, some here WITH and testing the bug fix. 
Of course you can ignore all that and keep assuming about bugs and when a fix will result without any of the data I have and reported if that makes you happier.

Fact: rare bug. Not solely Adobe code.
Fact: bug will be fixed properly and released when Adobe feels that is prudent.
Fact: work still being done, bug fix means build needs internal then external beta testing.
Fact: rushing one fix can introduce other bugs if the process is rushed without this process. Is that what you want to see?
Fact: Patience is a virtue.

[COBill]

Andrew,

You are wasting your time. Millions of Lightroom users are not having these issues while a few dozen are. We know where the problem lies.

Sure Lightroom, like all software, has bugs. They will be prioritized with all the other development work. What's #1, migrating to the new Apple hardware and software as that is of benefit to millions. 

People who think that their problem should be #1 live in a dream world. 

[thierryn48516695]

@andrew_rodney 

I agree with all your facts

But if you do not understand that when a bug happens only on some configurations, your best shot is to get this configuration ONE COMPUTER to start, compile with debug enabled and track/disable modifications between versions, then you just show that you have 0 experience in software development, even if I have no problem to recognize that you are an expert in color management.

Not tracking the bugs on the configuration where it happens is equivalent to start a 5 years PHD about heart when you are facing someone having a  heart attack.

Kind regards
Thierry

[COBill]

Thierry, 

Don't you find it strange that the bugs occur so rarely? That identical systems don't have the problems? Your comments demonstrate that you are the one with zero experience in software development. 

[FloCal]

Using Adobe softwares since the 90s as well, I don’t remember having met such a situation before. I know nothing about software debugging but I see what I see. More than 7000 users have viewed this thread and there are a couple of others on the same topic (and many don’t post a comment when they see that many others did). Thus, the number of affected customers may be much higher than what was heralded by some commentators down here. And professionals are also influencers. If a reasonable number of them is angry, it can be a rather noisy sounding board likely to reach the ears of shareholders.

Last Update from Rikk on 01/12/2021:

The Lightroom Classic team continues to work on a permanent fix for this issue. It is a top priority.  Stay subscribed to this thread as it will be your best conduit for information regarding this issue.

That was almost 3 weeks ago…

So, to be practical, there are roughly 3 scenarios (as far as I'm concerned) :

• Either they don't care (estimated chances: 10%, I am relatively confident in Adobe's commitment to their professional customers).
• Either they do care but they don't find a fix and never will (estimated chances: 10%, I am relatively confident in Adobe’s ability to do it - even if it’s an Apple-Adobe problem).
• Or they do care and they are going to find a fix (estimated chances: 80%, I am relatively confident in Adobe’s abilities and commitment to their professional customers), in which case they should tell us what’s going on. If not, since I’m getting old and the covid is lurking around, I won’t wait till the end of (my) time and certainly will look for other upgradeable solutions for my photos in a medium term. And too bad if it’s less convenient.

[thierryn48516695]

There is nothing "strange" in bugs that appear now and then.

Bug appear from Mac Pro 2010 to Mac Pro 2020 as you can see on this thread.

For the rest of your post, nothing to add. 

[engine54]

I am using iMac (Retina 5K, 27-inch, 2020)

3.8 GHz 8-Core Intel Core i7

64 GB 2667 MHz DDR4

AMD Radeon Pro 5700 XT 16 GB

Lightroom and Photoshop (latest versions) are now running SO slow, and making the iMac generally run incredibly slow. Unusable.

What is the cause and is there a fix?

[thierryn48516695]

Hi

for @bill_3305731 you have a too old hardware

for @andrew_rodney Adobe has been working hard for 3 months to find a very tricky bug

Hoping that you do not have processed too many photos with LR V10 (because V10 catalog cannot be read by previous version), going back to V9.4 is the safest solution.

Best and kind regards
Thierry

[Victoria Bampton LR Queen]

There's a limit to what staff are allowed to say without the lawyers getting involved. Since I'm not on the payroll, I think I can get away with sharing this much:

They do care greatly and it is the team's priority right now, but in a company the size of Adobe, it's like turning an ocean liner. They can't be as nimble as small companies, so the whole find/fix/test/release procedure takes a lot longer than any of us would like. 

[TheDigitalDog]

@photostudiotnk Adobe has been working hard for 3 months to find a very tricky bug.

No, find then fix, then test the fix internally, then test the fix externally. 

Those of us working in the bug find/fix trenches of course are aware of the process. Others can assume..... 

[thierryn48516695]

Many thanks for this scoop: you have to find the bug before fixing it.

Another great void contribution

[TheDigitalDog]

Many thanks for this scoop: you have to find the bug before fixing it.

Yes, didn't take 3 months as assumed and then posted (another great void contribution).

”Facts are stubborn things; and whatever may be our wishes, our inclinations, or the dictates of our passion, they cannot alter the state of facts and evidence.”

John Adams

[thierryn48516695]

I apologize:

For finding the bugs, setting up a fix, testing the fix internally and then externally, after three months, it it not done.

3 months is more time than the delay between V9.4 (june-august 2020) and V10 (october 2020). This also is a fact.