| | | | | Browse by category |
Article ID: 1015
Last updated: 29 Jan, 2008
Problem
Threads.h++ appears to have a memory leak when compiled with POSIX Threads.
Cause
Threads.h++ made repeated calls to
Action
The memory leak was corrected in Threads.h++ version 1.2.3. You should download the latest version of Threads.h++ and your other products in order to address this issue.
Threads.h++ appears to have a memory leak when compiled with POSIX Threads.
Cause
Threads.h++ made repeated calls to
pthread_attr_init() within it's code, however it was not explicitly calling pthread_attr_destroy() in order to release those resources. This resulted in a small memory leak when threads were being created.Action
The memory leak was corrected in Threads.h++ version 1.2.3. You should download the latest version of Threads.h++ and your other products in order to address this issue.
This article was:
Helpful |
Not helpful
Report an issue
Article ID: 1015
Last updated: 29 Jan, 2008
Revision: 1
Views: 2930
Posted: 19 Jul, 1999 by
--
Updated: 29 Jan, 2008 by
Others in this category
Why won't the InfoBrowser contents update in response to selection changes in ClassView or FileView?
Powered by KBPublisher (Knowledge base software)