forked from daptiv/log4net-loggly
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory Leak with log4net-loggly #27
Comments
Thanks @varshneyjayant we'll take a look when we get a chance |
We are having the same issue in a WebApi project. Memory gets filled with an ever increasing number of string[]. Removing the |
Thanks we are investigating this issue |
See the new library version here |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
We experience a memory leak in our WCF application when we have log4net-loggly enabled (see attached MemLeakConfig file).
MemLeakConfig.txt
Removing all references to the
LogglyAppender
in our config file stopped the memory leak (see attached NoMemLeakConfig file).NoMemLeakConfig.txt
Has anyone else experienced similar? Does anyone see issues with the first config that might cause this? Does anyone have any troubleshooting suggestions?
Thanks in advance!
The text was updated successfully, but these errors were encountered: