Dominik Psenner (JIRA | 20 Jul 22:10 2014
Picon

[jira] [Comment Edited] (LOG4NET-436) OutOfMemoryException


    [
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
(Continue reading)

Dominik Psenner (JIRA | 20 Jul 22:08 2014
Picon

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


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

Dominik Psenner commented on LOG4NET-436:
-----------------------------------------

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
(Continue reading)

Daniel Kugel (JIRA | 18 Jul 16:11 2014
Picon

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


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

Daniel Kugel commented on LOG4NET-436:
--------------------------------------

Can you share the full stack trace and perhaps the dump file?

> 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"
(Continue reading)

Cristian Gavrilut (JIRA | 18 Jul 10:38 2014
Picon

[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)

(Continue reading)

Isaac Devine | 4 Jul 04:37 2014
Picon

[PATCH] Add support for iOS and Android with Xamarin

Hi,

I'm not entirely sure about your contribution rules/guide so I've created an issue here:

https://issues.apache.org/jira/browse/LOG4NET-435

This contains patches to add support for iOS and Android on the xamarin platform.

Additionally it includes a patch to add an appender for the built-in Android Debug log.

Please let me know if I have missed something or if there is anything you want me improve on the patchset.

Cheers,
Isaac

P.S. I've subscribed to the development list after I created the JIRA issue, so I can't reply to that email
sorry. 

Isaac Devine (JIRA | 4 Jul 04:29 2014
Picon

[jira] [Updated] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets


     [
https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Isaac Devine updated LOG4NET-435:
---------------------------------

    Attachment: port-to-ios-and-android.patch
                android-log-appender.patch

Patches to add support for iOS and android and also a new appender for the built-in android log.

> Port log4net to Xamarin Android and Xamarin iOS targets
> -------------------------------------------------------
>
>                 Key: LOG4NET-435
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-435
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders, Builds
>    Affects Versions: 1.3.0
>         Environment: Xamarin, Android, iOS
>            Reporter: Isaac Devine
>              Labels: patch
>         Attachments: android-log-appender.patch, port-to-ios-and-android.patch
>
>
> Patches to support Xamarin Android and Xamarin iOS projects.
> Also includes an appender that will log to the built-in Android Log.

(Continue reading)

Isaac Devine (JIRA | 4 Jul 04:27 2014
Picon

[jira] [Created] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

Isaac Devine created LOG4NET-435:
------------------------------------

             Summary: Port log4net to Xamarin Android and Xamarin iOS targets
                 Key: LOG4NET-435
                 URL: https://issues.apache.org/jira/browse/LOG4NET-435
             Project: Log4net
          Issue Type: Improvement
          Components: Appenders, Builds
    Affects Versions: 1.3.0
         Environment: Xamarin, Android, iOS
            Reporter: Isaac Devine

Patches to support Xamarin Android and Xamarin iOS projects.

Also includes an appender that will log to the built-in Android Log.

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

Robert Sevcik (JIRA | 23 Jun 22:56 2014
Picon

[jira] [Comment Edited] (LOG4NET-83) Allow flushing into file every X milliseconds


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

Robert Sevcik edited comment on LOG4NET-83 at 6/23/14 8:54 PM:
---------------------------------------------------------------

I called it Keep-alive appender (KeepAliveAppender). It's implemented in log4net.Ext.Json for now. I'm
hopeful it will get accepted into log4net trunk.

https://sourceforge.net/p/log4net-json/wiki/keep-alive%20appender/

was (Author: robajz):
I called it Keep-alive appender (KeepAliveAppender) now. It's implemented in log4net.Ext.Json for now.
I'm hopeful it will get accepted into log4net trunk.

https://sourceforge.net/p/log4net-json/wiki/keep-alive%20appender/

> Allow flushing into file every X milliseconds
> ---------------------------------------------
>
>                 Key: LOG4NET-83
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-83
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: All
>            Reporter: Tal G
(Continue reading)

Robert Sevcik (JIRA | 23 Jun 22:56 2014
Picon

[jira] [Commented] (LOG4NET-83) Allow flushing into file every X milliseconds


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

Robert Sevcik commented on LOG4NET-83:
--------------------------------------

I called it Keep-alive appender (KeepAliveAppender) now. It's implemented in log4net.Ext.Json for now.
I'm hopeful it will get accepted into log4net trunk.

https://sourceforge.net/p/log4net-json/wiki/keep-alive%20appender/

> Allow flushing into file every X milliseconds
> ---------------------------------------------
>
>                 Key: LOG4NET-83
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-83
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: All
>            Reporter: Tal G
>            Priority: Minor
>             Fix For: 1.2 Maintenance Release
>
>
> In FileAppender you can specify either immediate flush on every message or not flushing at all.
> Immediate flushing reduces performance in 10% - 20%, but when flushing is skipped, then it is likely that
(Continue reading)

Dominik Psenner (JIRA | 5 Jun 10:22 2014
Picon

[jira] [Commented] (LOG4NET-429) Pattern with Context property causes severe slowdown


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

Dominik Psenner commented on LOG4NET-429:
-----------------------------------------

Your patch makes sense, but flattening a dictionary may no longer produce a flattened dictionary. Thus,
"there be dragons". And after all I might be wrong - my memory is not one of the best. :-) What if you used the
debugger to step through and check whether your patch works against the code above?

> Pattern with Context property causes severe slowdown
> ----------------------------------------------------
>
>                 Key: LOG4NET-429
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-429
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.13
>            Reporter: Jonas Versén
>            Assignee: Dominik Psenner
>            Priority: Minor
>              Labels: performance
>         Attachments: LOG4NET-429-alternative.patch, LOG4NET-429.patch
>
>
> If you use a context property in your appenders pattern, there will be a significant logging slowdown. In
my experience anywhere from 3 to 5 times slower (this will depend on the appender).
(Continue reading)

Stefan Bodewig (JIRA | 4 Jun 17:27 2014
Picon

[jira] [Commented] (LOG4NET-429) Pattern with Context property causes severe slowdown


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

Stefan Bodewig commented on LOG4NET-429:
----------------------------------------

Hmm. in that case any patch that tried to generalize laziness would become pretty convoluted.  Let's stick
with your original patch.

> Pattern with Context property causes severe slowdown
> ----------------------------------------------------
>
>                 Key: LOG4NET-429
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-429
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.13
>            Reporter: Jonas Versén
>            Assignee: Dominik Psenner
>            Priority: Minor
>              Labels: performance
>         Attachments: LOG4NET-429-alternative.patch, LOG4NET-429.patch
>
>
> If you use a context property in your appenders pattern, there will be a significant logging slowdown. In
my experience anywhere from 3 to 5 times slower (this will depend on the appender).
> I believe that as soon as you use a context property log4net will internally access the windows user name
(Continue reading)


Gmane