P: Slow UI when using Mac and Custom Display Profile

@DYP What profiling software did you use to make your profile? My profile from i1Profiler doesn't have a "unicode name" that I can find, and my profile also slows down the scrolling speed in LR.

I realize it is a very complex issue, and I did not realize that it affected such few users. While I did not expect the unicode name to have any affect on performance it seems to have. 

@photostudiotnk

You tested hundreds of combinations VS the literally billions of hardware/software platform combinations that exist for the Mac. That's like saying row boat testing helps in the development of an aircraft carrier. 

Yes but your custom profile was just as slow on my system as my custom profile.

Which is why, it's not the profile per se as it's not slow on this end. 

This is a very complex issue that involves a lot of moving objects; perhaps the display itself, video card, GPU, display resolution etc. It affects few users (compared to the user base). 

Let Adobe engineering do it's job. Supply via pre-release whatever they ask you to supply. Don't assume they don't care or are not working on a fix. It's untrue and doesn't serve yourself as a tester or your audience here. 

@photostudiotnk 

Now my questions to you.
What do you know about software development?
What is your personal experience?

I'm a partner in a software company (Pixel Genius) that produced three Photoshop Plug-in's and  two for Elements, and some of our sharpening code was licensed by Adobe for LR and ACR. Which means, my company and I have worked with Adobe engineering down to the code level. 

Last question: are you paid by Adobe as a beta tester?

No. 

Yes but your custom profile was just as slow on my system as my custom profile.

@DYP My custom profile has a UniCode Name, my custom profile has no issues with V10. It's not that. 

Dear @andrew_rodney another answer to your posts...

So you are a beta tester. OK

Now my questions to you.

What do you know about software development?
What is your personal experience?

Testing a software before release is not beta testing: it is having non regression routines that are launched after each modification, that run every night, with simulators to have all the possible machines/software configurations.

Even in OpenCascade, with only 120 employees,it was our process 20 years ago, with hundreds of possible configurations.

So, again, in this domain, what is your own experience and knowledge?

Last question: are you paid by Adobe as a beta tester?

I got to comparing sRGB with my custom profile. I noticed one thing that the sRGB profile did not have a UniCode Name: while the custom profile did. This may be a fluke but I removed the UniCode Name: from my custom profiles and saved them. I opened up up 10.1R4 and it seems there is some difference. I can't believe it would make a difference but others can test that as well.

You do not need to know the internal processes of Adobe to just see that V10 should not have been released and that QA is 0.

More assumptions like the number of actual V10 users versus the numbers who've uncovered this bug. Again, it runs just fine on my Mac as did all the betas. No software is bug free. There is a bug here, it will  get fixed. It's very rare in that of the massive user base, we hear some here reporting it, it wasn't reported inside of Adobe or outside during beta. 

I'm sorry the facts of how this process works, one you have zero experience with, ruined your day.