[
https://issues.apache.org/jira/browse/LOG4NET-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-436.
-----------------------------------
Resolution: Cannot Reproduce
Closing this again with cannot reproduce after a year and a half of no
activity. I assume this to be noise caused by a memory leak in the application
that uses log4net.
> 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
> Labels: OutOfMemoryError, outofmemory
>
> 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.3.4#6332)
