Agent 2.1.1.1 (OcsService.exe) uses increasing number of handles in XP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OCS Inventory: Windows Agent |
In Progress
|
Undecided
|
Unassigned |
Bug Description
Yesterday, I noticed a Windows XP machine getting sluggish and found OcsService.exe using more than 27,000 handles. I restarted the service which started out with 128 handles and a day later it is now over 1,500 handles and growing. Another machine shows OcsService.exe with 18,800+ handles. I see this becoming a problem on workstations or servers that are not rebooted every day.
I Recently upgraded the client on a number of machines and am worried about the long term effects of this handle leak. Memory usage seems fine but the handles count keeps growing. I've tried to see what it's doing on Windows 7 but on the 2 I've checked, it shows the OCS Inventory Service is stopped although inventories seem to continue to be updated daily for these machines. How can inventory be reported if the service is not running? I just checked another Windows 7 machine and it show the OCS Inventory Service is running but I don't see a way to list open handles for services in task manager. Any pointers here would be helpful.
By the way, a Windows 2000 Server with OCS Agent v4.0.3.1 and 3 months uptime shows 639 handles.
tags: | added: agent |
tags: | added: 2.1.1.1 |
Changed in ocsinventory-windows-agent: | |
status: | New → In Progress |
I can confirm the leak on Windows XP. The rate appears to be exactly 1 handle per minute.
On a Windows 7 64 bit machine, the amount of handles remains nearly constant about 138. BTW, I used "Process Explorer" to inspect the process.