Loading...

log4net-dev@logging.apache.org

[Prev] Thread [Next]  |  [Prev] Date [Next]

[jira] Commented: (LOG4NET-192) Memory leaks with large multi-threaded application in log4net DLL 1.2.0.30714 Vibha Kapur (JIRA) Thu Jan 15 08:01:04 2009

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

Vibha Kapur commented on LOG4NET-192:
-------------------------------------

We get following exception in our application log file:
Caught Exception: [Exception of type System.OutOfMemoryException was thrown.] 
for Type [System.String]
Exception: System.OutOfMemoryException
Message: Exception of type System.OutOfMemoryException was thrown.



We have given following log4net configuration in our application config file:
<LogAndTrace>
                <Log4Net>
                        <LoggerDefinition 
FileName="StrideSmartRouterAppLogs.config" FilePath="C:\Program 
Files\Elind\Stride\FIXGateway\SRBinaries" Severity="Debug" />
                </Log4Net>
        </LogAndTrace>



We used to windbg tool to analyse the issue. We could see lot of log4net 
objects into wait state via SYNCBLKALL command. Here are top 15 rows:
Index SyncBlock MonitorHeld Recursion   Thread  ThreadID     Object Waiting
    1 0x00000000                                             0x01093178
    2 0x001967e4            0         0        0     none    0x01099c14 
System.ServiceProcess.NativeMethods/ServiceMainCallback
    3 0x00196810            0         0        0     none    0x01099c4c 
System.ServiceProcess.NativeMethods/ServiceControlCallbackEx
    4 0x07eaf5b4            0         0        0     none    0x011383f8 
log4net.Repository.Hierarchy.DefaultLoggerFactory/LoggerImpl
    5 0x00000000                                             0x0112f4dc
    6 0x00000000                                             0x01130a48
    7 0x001968c0            0         0        0     none    0x01132fa4 
log4net.Repository.Hierarchy.DefaultLoggerFactory/LoggerImpl
    8 0x00196894            0         0        0     none    0x0113518c 
log4net.Repository.Hierarchy.DefaultLoggerFactory/LoggerImpl
    9 0x07d71bb8            0         0        0     none    0x01138460 
log4net.Repository.Hierarchy.DefaultLoggerFactory/LoggerImpl
   10 0x03df9770            0         0        0     none    0x011384c4 
log4net.Repository.Hierarchy.DefaultLoggerFactory/LoggerImpl
   11 0x00000000                                             0x01365614
   12 0x00000000                                             0x01a160f8
   13 0x07de5d30            0         0        0     none       22501 Free
   14 0x1069bdbc            0         0        0     none         492 Free
   15 0x00000000                                             0x015096a4



I analysed stack trace also at some basic level but did not get much info out 
of that.
I am mailing my applicatin's Dumpstack at the yahoo ID mentioned in your 
profile.

> 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.