Skip to content
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 possibly?? #19

Open
mp1smw opened this issue Feb 18, 2016 · 2 comments
Open

Memory leak possibly?? #19

mp1smw opened this issue Feb 18, 2016 · 2 comments

Comments

@mp1smw
Copy link

mp1smw commented Feb 18, 2016

I have only just started testing this sever so maybe I am doing something stupid but it would be good to know what if I am! I am running the Dev branch of the server dll and using the demo project WebDAVSharp.FileExample in a simple console application mode. I have tested both in debug and release mode outside of VS and find that the memory utilization is ramping up to 6GB so far after transferring 66,000 files into the server. Once it gets much higher the application hangs. Am I doing something stupid? Is there some in memory database keeping track of stuff or is it a real leak?
Any thoughts would be appreciated.

@springy76
Copy link

I just noticed the same thing. I first thought it's because of the internal cache, but after disabling the cache, it becomes even worse. After enumerating 20,000 file infos the GC became busy and did not stop after serveral minutes.
I wonder if the cache has been implemented for more speed or to "save" memory due to memory leaks.

@bjorn-ali-goransson
Copy link

Can you give some instructions on how to reliably replicate this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants