1
Reply
Were you able to resolve this issue on your own yet?
If not, here are some insights.
Just about an hour ago from writing this messgae, I've experienced the same issue. I am on Micrososft Windows 11 and using Adobe Acrobat Pro DC version, Continuous Release 2024.001.20629 (64-bit).
See my slide:
At a first glance the problem seems to be triggered by one of the ARM (Adobe Reader and Acrobat Manager) processes. But there is more to and it gets really technical the more you dig about it.
Adobe Acrobat community users have been reporting issues with the Adobe AcroCEF executable (AcroCEF.exe) and observing that it consumes high CPU resources.
Discussions about this complex topic can be traced back in these community forums as far as 2015 (maybe earlier dates, as illustrated in this old article: Adobe Using Google Chromium Embedded Framework Adobe Using Google Chromium Embedded Framework (and a little more insights here : CEF integration in Dreamweaver ).
I am not sure what causes this but following this guidance from Adobe Help Center allowed me to continue to work with Acrobat instead of manually forcing the Acrobat program to quit:
However, I've decided to terminate the whole process tree for the AcroCEF process (which recreates itself anyway), instead of terminating the "Acrobat.exe" tasks.
Doing so, it allowed me to see the process that was duplicating itself on top of an older tree process; getting rid of that tree process (as shown in my next slide below), it immediately allowed me to continue to work without loosing all of my recent files that are listed in the Acrobat's Home View ==> Recent (learned this the hard way in the past):
This method worked a treat for me.
The best explanation I could find to this issue is explained further in this other Adobe Helpx guidance:
Note at the end of the article, that it emphasizes on the browser reporting an incorrect condition, specifically mentioning about Internet Explorer, which at present, it is not fully phased out of Microsoft Edge on Windows 11.
In fact, I wasn't using Microsoft Edge when this happened, but a set of logs were automatically added to the C:\Windows\Temp folder. See next slide:
As you can tell, the processes that I highlighted inside the red rectangles, all were created chronlogically in a sequence, and almost at the same time.
I am posting this just for the sake of those other users who might be reading and have seen this behavior before in their own Windows machines.
Perhaps, someone can share more insightful tips., please ?!?!?
Anyway, as I inspected those logs I did notice that Chrome was updating or patching itself (specifically Microsoft Edge), which explains the assistance in unison from both AdobeArm processes since they do assist the AcroServicesUpdater during patch updates and installation of Windows Installer fies.
And the important detail here is, as I mentioned earlier, that these logs generated on their own at the same time ( noted in my screenshot above), but I wasn't installing the AdobePDF Maker as a printer, and I wasn't using Google Chrome as a web browser, I was using Mozilla Firefox.
.
However, last night I was playing around with the new Microsoft Edge web browser in a different desktop computer, where I was able to test the Acrobat Reader extension for that new browser (which uses the Adobe PDFMaker Add-On to produce and handle the conversion of files to PDF and vice versa).
Furthermore, this issue triggered today as soon as I opened the Microsoft Edge web browser on this PC (which I barely use on this computer). I only use Office365 applications such as, Web Outlook which is tightly integrated with the MS Edge web browser.
That alone confirms, in my humble opinion, that this Chromium Extended Framework tracks you as an individual, and identifies you personally when you install an Adobe add-on extension to the Microsoft Edge browser (either from the Chrome Webstore or the MicrosoftEdge store). It has its own convenience, but I understand now why so many users in this community have expressed disappointed and discontent. Specifically with these continued crashes and making it really hard for the average power users to figure out on their own what is happening.
Even funnier, but nevertheless creepier, I was testing the Adobe acrobat extension on an ungoogled version of the Chromium Web browser on a Linux computer... in which case, I did installed manually the Adobe Acrobat extension successfully on that particular web browser and without having to be signed in to the Google Chrome Webstore... Just food for thought.
AdChoices