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

Large repository crashing cvs2svn.py and possible memory leak?

From: Nathan Sharp <spamnps+subversion_at_phoenix-int.com>
Date: 2002-12-18 15:02:07 CET

I'm currently testing out subversion on a test box here (RedHat 8.0) and
have been very impressed so far. I'm quite excited to employ it on a
real project, but am having problems importing our large CVS repository
into it. Our CVS repository goes back to 1996 and is 2.2GB on disk.
 The cvs2svn.py script successfully runs through the first thee passes
but fails with a segementation fault in the fourth pass. The repository
it generates is valid up until the point it crashes (somewhere in 1999)
and it doesn't seem to crash at the same spot if I re-run it. One thing
I noticed was that as the script runs, it takes increasingly more and
more memory as it goes, was up to almost 400Meg last I checked before it
crashed. I'm suspicious that perhaps it just runs the computer out of
memory (it isn't a real powerful box, it is just for testing), but I
don't have any real evidence to that fact.
I'm running:
svn HEAD as of a couple of days ago
python 2.2.1-17 RPM
swig 1.3.16 from tarball
viewcvs HEAD as of a couple of days ago
Berkely db 4.0.14-14 RPM

Any advice for debugging this? I ran the script w/ a -v and the reports
it generates seem O.K. up until it crashes, at which point the output
ends abruptly mid-line w/ no other errors. The shell reports the
segmentation fault. No core file is generated.

Thanks again!

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 18 15:03:47 2002

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