Re: repos corruption revisited: memory leak?

"Jan Hendrik" <jan.hendrik@bigfoot.com> writes:

> Can this be a memory leak? As a non-programmer I have no real
> idea what this is, but it seems so unlikely to me that a small
> commit works, but directly thereafter the update of the other
> working copy resulting from this not. And not once, but repeatedly
> and constantly. And that _ANY_ command to the repos ends in
> corruption while the HDD rotates like mad. After 35 update/commit
> cycles of quite different sizes had worked flawlessly.

I've been testing for memory leaks all week, using very large trees
(the 340meg mozilla tree, with 42,000 smallish files), and I can't
*ever* make httpd grow large.

When I do an import of the mozilla tree, or a checkout, update,
commit... httpd always stays at a tiny 10 megs or less. We found some
*client* memory leaks (which are now fixed in svn 0.32), but never a
server-side leak.

So I'm completely at a loss to to understand why you're seeing these
huge httpd memory sizes. The only difference is that your apache is
running on win32, and mine on Linux.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 23 16:49:55 2003