Hello! As I wrote a message about access rights problem before, now I will write another message that will explain a reason for us to try to update (unplanned update) to SVN v1.7.0.
We had used SVN v1.6.5 server (CollabNet build) on Windows 2003 x64 with 4GB RAM. Yesterday SVN server is stopped unexpectedly. I tried to restart it, but behaviour was: immediately after start it created about 800-900 threads, and allocate about 800-900mb of memory than stops (or crashes; but seems, stops with error that there no resources -- I can's say exactly for all cases, just I saw this error later with 1.7.0 in my debugging experiments). Due to some expiriments it was not possible to understand the reason of such behaviour. The main idea is simple - some "floating" bug in svnserve.exe, that cause to enter in such buggest state with allocation infinity amount of resources (threads/memory). So, we decide to update to SVN v1.7.0 (unplanned). It started ok, and used about 5-24mb of memory, 3-34 threads, no more. But after some unknown events it falled to the same behavior: - stops with no enough resources - after restart: immediately try to create about 800-900 threads and allocate 800-900mb of memory, then stops. I tried to investigate problems, using different cases, removing some of repositories, setting them back, analyzing caches, tried to reproduce this problem under debugger, but was not success. I made a lot of experiments, but cannot understand the reason of the problem, anyway, after a lot of hours of shamanism this issue is not reproduce on our system again. Someone seen something similar to this? Any ideas? Just interesting. -- С уважением, Andrey mailto:and...@online-solutions.ru
