[
https://issues.apache.org/jira/browse/LOG4NET-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068032#comment-14068032
]
Dominik Psenner edited comment on LOG4NET-436 at 7/20/14 8:09 PM:
------------------------------------------------------------------
There is one way to find out if it is fixed in the latest release: try it out.
I was unable to reproduce the issue a year ago, but maybe we can do so this
time. We require either a sample application to memory profile the root cause
or a memory profiler evaluation from your side.
was (Author: nachbarslumpi):
There is one way to find out if it is fixed in the latest release: try it out.
I was unable to reproduce the issue a year ago, but maybe we can do so this
time. We require either a sample application to reproduce the issue an memory
profile the root cause or a memory profiler evaluation from your side.
> 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.2#6252)
