DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14723>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14723 Memory leak in atomicOpsMutex Summary: Memory leak in atomicOpsMutex Product: Xerces-C++ Version: 2.1.0 Platform: All OS/Version: All Status: NEW Severity: Minor Priority: Other Component: Utilities AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] For several platforms, there exists an XMLMutex named atomicOpsMutex. This object is a global with static scope, and should have its constructor executed on startup. After its constructor has finished, atomicOpsMutex.fHandle should point to a valid mutex. XMLPlatformUtils::platformInit() will re-assign atomicOpsMutex.fHandle without checking if the pointer is non-0, thereby leaking the initial mutex. This occurs on Linux, FreeBSD, HP-UX, and IRIX. I made a simple conditional in each offending source file: if (atomicOpsMutex.fHandle == 0) { atomicOpsMutex.fHandle = XMLPlatformUtils::makeMutex(); } --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
