You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: