Activity for log4cplus
-
SourceForge Robot created a blog post
v2.1.2
-
log4cplus released /log4cplus-stable/2.1.2/ChangeLog-README.md
-
-
-
-
-
-
-
-
-
-
-
-
-
v2.1.0
-
v2.1.1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Václav Haisman modified a wiki page
ProjectStatus
-
Release
-
Release
-
Home
-
CodeExamples
-
v2.1.0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
v2.0.8
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Home
-
Home
-
Home
-
Home
-
v2.0.7
-
v2.0.7
-
v2.0.7
-
-
-
-
-
-
-
-
-
-
-
-
-
-
v2.0.6
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Guglielmo Fanini modified a comment on ticket #335
I am observing memory leaks in log4cplus version 2.0 compiled as static library with windows visual studio 2015, logging only to a rolling file, not console or other appenders, since I cannot terminate the thread which needs to run continuosly in a server, should I call log4cplus::threadCleanup() periodically or what ? This is in a pre existing project I am working on it's not my choice.
-
I am observing memory leaks in log4cplus compiled as static library with windows visual studio 2015, logging only to a rolling file, not console or other appenders, since I cannot terminate the thread which needs to run continuosly in a server, should I call log4cplus::threadCleanup() periodically or what ?
-
I am observing memory leaks in log4cplus compiled as static library with windows visual studio 2015, logging only to a file, not console or other appenders, since I cannot terminate the thread which needs to run continuosly in a server, should I call log4cplus::threadCleanup() periodically or what ?
1 >
