win32-name-event-objects-20040228
authorJeffrey Altman <jaltman@mit.edu>
Sun, 29 Feb 2004 02:38:26 +0000 (02:38 +0000)
committerJeffrey Altman <jaltman@secure-endpoints.com>
Sun, 29 Feb 2004 02:38:26 +0000 (02:38 +0000)
commit85caa4d1ded464b2d89eb8d2a14a6cedf93de08c
tree895ea24f5a064307fe536395e165755e687903ce
parentd83b9bb75aac67ef79857b731e421dbb6168311f
win32-name-event-objects-20040228

This is a very bad leak of Event Objects.  Name all of our event objects
in an attempt to identify the source of the leak.  Apparently, the leak
is not coming from any Event Objects we are creating directly.

Did find a misallocation of event objects in the smb code for the
initial session object.  Fixed.
src/WINNT/afsadmsvr/TaAfsAdmSvrCallback.cpp
src/WINNT/afsd/NTMakefile
src/WINNT/afsd/afsd_flushvol.c
src/WINNT/afsd/afsd_service.c
src/WINNT/afsd/smb.c
src/WINNT/afssvrmgr/alert.cpp
src/WINNT/bosctlsvc/bosctlsvc.c
src/WINNT/pthread/pthread.c