P: Slow UI when using Mac and Custom Display Profile

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

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

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. 

@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

"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? 😉

Reminds me of the quote:

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

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.

@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

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>

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!