Token and Process Handle Leak

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install the DLL
2. Reset Passwords (the more resets, the bigger the problem)
3. Use Process Explorer to look at the handles in the lsass.exe process

What is the expected output?
Normal number of tokens and process handles

What do you see instead?
Inflated number of handles, with many process handles to not existent processes 
and token handles for the syncing account.

What version of the product are you using?
The most recent version from the source, with some local edits (which attribute 
to use, some error handling in the C# application, running a second custom 
process by replacing the original process with a batch file and having the 
batch call GoogleHashUpdater and our custom process). 

On what operating system?
Windows 2003 SP2

Please provide any additional information below.

Eventually, the server will stop responding properly to LDAP and authentication 
requests. A reboot will fix the problem. The server complain about drive space 
issues, however there is plenty of space. I believe this is a misleading error, 
as the handles are full, not the drive.

I'm working on reproducing it on a separate Domain controller, and I'll try 
with unchanged code, but I have another deadline before I can work on this.

Original issue reported on code.google.com by evervis...@gmail.com on 26 Mar 2012 at 5:37

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The account we run it with has a 20 character password, and as of December 
2012, we unified our password policy across multiple domains and other 
applications, to between 8 and 20 characters. I just checked one of our domain 
controllers, and we still have the problem, and it hasn't been restarted since 
december 2012 (this one doesn't process alot of password changes).

Original comment by evervis...@gmail.com on 28 Feb 2013 at 7:49