Skip to main content
Participating Frequently
September 18, 2013
Question

High CPU and memory usage after Add-in update to 11.2.385.0

  • September 18, 2013
  • 5 replies
  • 14210 views

After last update Add-in leaks memory when switching layouts and has high CPU usage (90-100%) all the time on more than 20 computers running different browsers, OSes etc. What can we do to make our environment usable again?

(we use adobe connect hosted option ver. 9.1.1, add-in version is WIN11.2.385.0)

This topic has been closed for replies.

5 replies

October 18, 2013

Hi All,

There is a workaround to resolve this issue. As it is related to modifying registry, please be very careful and take backup of your registry first.

The workaround is to set the value of "Disable Performance Counters" to 0 @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfProc\Performance

If this registry entry is not present, create one. Meanwhile, we are working on fixing this issue.

Hope this helps!

Thanks,

Deepika

PS: Edit the Registry at your own risk. Inappropriate changes to the Windows Registry can disable the operating system! To safeguard against such an accident, back up your existing registry by choosing Registry » Export Registry File after launching the Registry Editor and before making any changes

Participating Frequently
October 18, 2013

Unfortunatelly this didn't resolve issue for me - the PF Delta dropped to 2-10 from several thousands but CPU usage is still at 25%

Additionally to registry fix described by Deepika you will need to rus as administrator "lodctr /R" which rebiulds performance monitor library then CPU usage drops to 1%

October 18, 2013

Thanks for the update Lukasz!

It is good to know that your CPU usage drops to 1% after applying the workaround.

To sum up, for Connect add-in to consume less CPU, as a workaround the performance monitor library needs to be rebuilt and "perfproc" provider should be enabled as follow:

"Click Start, type cmd right click cmd.exe, and select Run as administrator.
At the prompt, type lodctr /r and press ENTER. This will repair the pointers (those are stored in the registry).

C:\Windows\system32>lodctr /r

Info: Successfully rebuilt performance counter setting from system backup store

After this action it is possible that perfproc providers are disabled. You can check the status with lodctr /q.

C:\Windows\system32>lodctr /q
Performance Counter ID Queries [PERFLIB]:

etc...


If it says (Disabled) next to perfproc  provider, you can enable it with lodctr /e:perfproc "

sameer_puri
Adobe Employee
Adobe Employee
October 17, 2013

Hi All,

Good News! We were able to reproduce the issue in-house and have started working on the fix now. Though i dont have any ETA about when this fix will be available to in an update, but be rest assured that whenever it will be provided(should be soon), it will fix the issue forever.

Stay tuned for other updates!

Thanks

Sameer Puri

Participant
September 19, 2013

Hi there,

I am having the same problem.

Case number: 0184702770

Adobe has sent me generic instructions on decreasing screen resolution, cleanup desktop, blah blah which is not helpful. My machine has been running fine with Acrobat Connect for four years and suddenly this problem appears. It does not happen on another machine with same screen res, network connection, etc. however it is running Win Server 2008 R2.

Here is my configuration and screen shot of task manager and resources monitor showing connect consuming bandwidth and being non-reponsive:

Nikhil Sharma
Adobe Employee
Adobe Employee
September 19, 2013

Hi Lucasz et al,

Can you please provide some info on the screen Resolution of the machien which is having this issue ?

(Assuming the CPU usage you have mentioned is with screen sharing) Also it would be great if you could describe a bit about :

a) CPU usage when nothing is being shared

b) And when one shares the screen

Regards

Nikhil

Participating Frequently
September 19, 2013

This issue is resolution independent (our machines vary from 1280x1024 to fullHD resolutions). The high CPU begins when Add-in starts and continues as long as Add-in is running and there is no difference if we share screen, webcam, voice or do nothing. Additionally changing layout add per change ~10MB of RAM used - the RAM is never freed.

September 19, 2013

We experience the same thing as Lukasz reports.

We have seen CPU temp on machines climb from 55 degrees C to

100 degrees C within 5 minutes of loading AdobeConnectAddIn.EXE on several occassions, that is with or without screen sharing, with AdobeConnectAddIn.EXE clearly using between 50-80% of CPU from point of startup.

We have seen CPU demand for AdobeConnectAddIn.EXE jump to 80%,

as soon as sharing MS WORD, but can't say would not happen without screen

sharing because we have seen the high CPU usage happen without screen sharing.

In general AdobeConnectAddIn.EXE aggressively consumes most or all available CPU driving general CPU use to 100% (ceiling usage).   This only began with ver. 11.2.385.0,

Our team has been have using Adobe connect intensively for 3 years w/o this sort of problem until ver. 11.2.385.0, was forced in Adobe connect upgrade window in the last 7-10 days.

Per screen resolution - 1200X1920

CPU Usage - 50% to 80% + experienced when loading add-in.

CPU heat increases - 40degrees celsius within 5 - 8 minutes of loading add-in.

Other : We do not use video or audio features of Adobe Connect.

Our primary desktop sharing is limited to MS Office and text based information sharing.

September 18, 2013

We are an on-premise environment and currently using Connect Add-in 11.2.385.0 and are on v9.0.4.  We have 8 App servers and each is experiencing high cpu usage as of late. 

Is this in relation to the Add-In 11.2.385.0 and what is being done to address this issue? 

September 18, 2013

Several people on our team have been complaining about 11.2.385.0,

crashes and systems driven to 100% CPU usage. 

Also we have seen machines heating up 10-20 degrees instantly when AdobeConnectAddIn.EXE is running, with temp running to 100 Celcius.

No other significant software is running on the machine, you will note

most other apps are on idle.

Soon after on this machine temps jumped to 100 and the machine shut down.