If for no other reasons stuff in here that is library routines (like QT) probably get a lot more attention to 64 bit code and performance lately than to 32 bit. Jotta voit analysoida Adobe CEF Helper.exe -prosessia tietokoneessa, seuraavat ohjelmat ovat osoittautuneet hydyllisiksi: Security Task Manager nytt kaikki kynniss olevat Windows-tehtvt, mukaan lukien upotetut piilotetut prosessit, kuten nppimistn ja selaimen valvonnan tai Autostart-merkinnt. Adobe CEF Helper 5.3 <<<<< Windows Explorer 1.
Start Media Player Heavy hitters are: Adobe CEF Helper 4.4 <<<<< Media player 1.4. After some preliminary testing, I had reason to suspect that Adobe might play a role in the problem.
Now does any of this matter, does any of it cause instability or performance issues? No idea, but it sure seems like a place worth looking. I used the Task Manager to monitor CPU usage. I'd bet heavily this is all just legacy code and Adobe doesn't consider it a priority to migrate to 64 bits. In addition all the following Adobe separate processes are still 32 bits. So why would Adobe have 2 of 4 child processes that are running still be 32 bits? Especially if they have indeed forced users to 64 bits? I am guessing that QT is what handles the actual UI - QT is a well known GUI development framework. Notice the two server processes in my task manager screen shot of LR 7.3.1 running a build preview.
Below are the list of Adobe background processes: CCLibraries CCXProcess Creative Cloud Desktop Coresync Creative Cloud PDApp.exe AcroTray AGSServices Navigate to the following directory. Yeah, they require 64 bits for the base product (I see now, thank you), but a bunch of stuff under the hood still runs as 32 bit. Close all Adobe processes and tasks running on the background from Task Manager (Windows) or Activity Monitor (MAC) except Adobe IPC Broker and CEF helper.