[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn eats all memory, OOM killer kicks in

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-04-15 20:51:23 CEST

"Kirby C. Bohling" <kbohling@birddog.com> writes:
> > Maybe we can think of some way to test for killability in the client?
> No that isn't exactly a portable solution (won't work on Windows). I
> don't know of anything else that gives you "killable" tests that are
> repeatable. Just an idea if you really want to try that. The worst
> thing about it is the warts in the code with randomFailure. We ended
> up moving it to an extremely low level library that everybody
> referenced and left it there. Then commented the heck out of it. I
> would guess that pool creation would be my chosen place in the SVN
> code.

We don't have to do random failures -- we can have chosen failure
points, set off by a special command-line flag (for example).

   $ svn --fail-point=LABEL ...

Then the tests would be repeatable. (Of course, we can use random
processes to help choose the points.)

We'd still have to have those conditional exits scattered throughout
the code, but it would be worth it IMHO.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 15 20:47:45 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.