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 "Cristian Gavrilut (JIRA)" <ji...@apache.org> on 2014/07/18 10:38:04 UTC

[jira] [Created] (LOG4NET-436) OutOfMemoryException

Cristian Gavrilut created LOG4NET-436:
-----------------------------------------

             Summary: OutOfMemoryException
                 Key: LOG4NET-436
                 URL: https://issues.apache.org/jira/browse/LOG4NET-436
             Project: Log4net
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.2.10
         Environment: OS: Windows 7 Professional; .NET 4.0
            Reporter: Cristian Gavrilut
            Priority: Blocker


I've noticed as on the same version a bug was opened which was closed with reason cannot reproduce:
https://issues.apache.org/jira/browse/LOG4NET-294 

Now we could reproduce constantly with our application but just on a single machine. I've collected a minidump with full memory as the application was sky rocketing on memory to 1.6 GB and then was throwing an out of memory exception. I found in the inner exception stacktrace that issue was coming from log4net ReaderWriterLock. I've disabled the log4net by using the suggested config: <log4net threshold="OFF" /> and then no exception any more.

The question is now if this issue is fixed in your latest version ?



--
This message was sent by Atlassian JIRA
(v6.2#6252)