You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Ron Grabowski (JIRA)" <ji...@apache.org> on 2009/01/12 23:27:59 UTC

[jira] Commented: (LOG4NET-192) Memory leaks with large multi-threaded application in log4net DLL 1.2.0.30714

    [ https://issues.apache.org/jira/browse/LOG4NET-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663126#action_12663126 ] 

Ron Grabowski commented on LOG4NET-192:
---------------------------------------

You going to have to give us a little more information. Have you considered upgrading to the latest version of log4net? I know that log4net doesn't release often by 1.2.0-beta8 was released in 2003. That would make it about 6 years old.

> Memory leaks with large multi-threaded application in log4net DLL 1.2.0.30714
> -----------------------------------------------------------------------------
>
>                 Key: LOG4NET-192
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-192
>             Project: Log4net
>          Issue Type: Bug
>         Environment: Windows 2003, .NET framework 1.1
>            Reporter: Vibha Kapur
>            Priority: Critical
>
> We've coded log4net (1.2.0-beta8) into our application. With log4net enabled we see our virtual memory increasing and never decreasing, over a period of time and particularly with stress testing the server runs out of memory and everything grinds to a halt.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.