[
https://issues.apache.org/jira/browse/LOGCXX-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thorsten Schöning resolved LOGCXX-301.
--------------------------------------
Resolution: Cannot Reproduce
Because we are trying to reduce the backlog of open issues, I'm closing this
one right now. The described environment in which the problem has been reported
originally is pretty outdated these days and things might have been fixed
already with a newer version of log4cxx and/or a new environment. If this
concrete problem is still relevant for someone, feel free to reopen and provide
the necessary details. Otherwise it's best to create a new issue describing the
new environment and problem.
> MSVC 8.0, log4cxx from dll = memory leaks messages
> --------------------------------------------------
>
> Key: LOGCXX-301
> URL: https://issues.apache.org/jira/browse/LOGCXX-301
> Project: Log4cxx
> Issue Type: Bug
> Affects Versions: 0.11.0
> Environment: MSVC 8.0 SP1, MFC, log4cxx from SVN, r673295
> Reporter: Alexey Kirjushkin
> Assignee: Curt Arnold
> Priority: Major
> Attachments: log4cxxleaks.zip
>
>
> Steps:
> 1. Create mfc exe, use log4cxx:
> PropertyConfigurator::configure(LOG4CXX_FILE( path ));
> LOG4CXX_INFO ( Logger::getRootLogger(), _T("testleaks.exe _tmain") );
> OK, no memory leak
> 2. Create dll, use log4cxx:
> extern "C" __declspec ( dllexport )
> void testlog()
> {
> LOG4CXX_INFO ( Logger::getRootLogger(), _T ( "logdlltest.dll testlog()"
> ) );
> }
> 3. from exe call testlog():
> PropertyConfigurator::configure(LOG4CXX_FILE( path ));
> LOG4CXX_INFO ( Logger::getRootLogger(), _T("testleaks.exe _tmain") );
> testlog();
> 4. Run exe (Debug configuration) and see after finish in Output MSVC 316 (!)
> memory leak messages
> attachment - Test solution (exe and dll)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
