I have found a handle leak within a Java client program on windows calling NotesThread.stermThread(). A simple program like the following reproduces it.
for (int i = 0; i < 2; i++)
{
NotesThread.sinitThread();
NotesThread.stermThread();
}
The real culprit seems to be NotesThread.stermThread(). If it gets called more than once, procexp (http://www.sysinternals.com/ntw2k/freeware/procexp.shtml)
shows that a number of Event and Section (memory mapped files) are leaked (which contribute to the handle count reported the task manager). If you pause the program after the for loop, and attach with procexp, this is easy to see. Increasing the loop count increases the number of leaked objects.
Very roughly, 10 Event and 10 Section handles are leaked each time stermThread() is called.
This is a bug, I have found with both 6.0.1 and 6.5.X under Windows 2000 and Windows XP.
The following is the only other reference I have seen reporting this issue.
I am worried about other resources leaking for programs which actually open databases and so forth.
Is this a known issue? I couldn’t see a place to report this bug.