Access Connections (AvSvc.exe) sucking up tons of handles...

[tbessie]

Recently, after some upgrades to my T400 (ThinkVantage and others), I noticed that network activity would start to be flakey. In particular, Firefox starts simply hanging after using it for some time, though there are other symptoms.

Looking with ProcessExplorer at handles per process, I noticed that the Access Connections service (AcSvc.exe)'s complement of handles kept growing... about every second it grew by 2!

Has anyone seen this behavior before? I'm not sure this is the culprit, but I'm mighty suspicious... it just keeps growing and doesn't stop. Very odd.

I'm using Access Connections v5.12 for Windows XP.

- Tim

[Marin85]

I don´t use AC, but there were some reports around about Lenovo Power Manager having a leak... but I guess that´s not really related to your topic...

[tbessie]

I don´t use AC, but there were some reports around about Lenovo Power Manager having a leak... but I guess that´s not really related to your topic...

Well, in general I'm trying to figure out why Firefox et. al. stop working after a bit, so it might be the power manager as well. I'll search for that and see what I can find. Thanks!

- Tim

[Marin85]

I even found that thread Power Manager consuming Handles? Leak? Try to ignore the yellow coloring

Marin

[AGoodSolution]

Since this was a general question about Access Connections sucking up resources, I've had CPU spikes with it while trying to initially connect with authorized networks upon boot up and it would drop connections without any particular pattern.

Finally just asked myself what the advantage of it was versus the included connectivity features of Windows and realizing none / uninstalled.

Other tools that may be helpful in figuring out what about Accessconnections is killing your system is filemon.exe and regmon.exe.

It sound like you're already using something like procexp or another decent debugger suite to figure out what you have so far and Filemon and Regmon have helped me figure out things like processes that won't stop trying to write to a file which may be locked by another process and the offensive process spikes the CPU with hyper attempts to write the locked resources.