[LOGCXX-140] Handle leak with LoggingEvent::getCurrentThreadName

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.10.0
• Fix Version/s: 0.10.0
• Environment: Win32
• Assignee: Curt Arnold
• Reporter: Kriz
• Created: 16/May/06 20:20
• Updated: 23/Oct/06 23:03
• Resolved: 23/Oct/06 23:03

Description

apr_os_thread_current leaks a handle for each spawned thread (see also documentation for revision 64133 of apr's win32/thread.c).

I suppose that the actual intend was to print the thread id in stead of the thread handle. It would be much more convenient to have the tid (thread id) because tools such as "pslist" print also this tid. The thread handle is not very meaningful at this point.

Since the Win32-API function GetCurrentThreadId() is not provided by the apr library, I suggest following (ugly) patch:
—
const LogString LoggingEvent::getCurrentThreadName() {
#if APR_HAS_THREADS
//return StringHelper::formatHex((const void*) apr_os_thread_current());
return StringHelper::formatHex((const void*) GetCurrentThreadId()); // CS 16-05-2006 due to handle leak
#else
return LOG4CXX_STR("0x00000000");
#endif
}
—