Christian Daudt <csd_ob@daudt.org> writes:
> Ok,
> ran into a completely different error doing the same test locally:
>
> subversion/libsvn_client/commit.c:670: (apr_err=160029)
> svn: Berkeley DB error
> svn: Commit failed (details follow):
> subversion/libsvn_fs/tree.c:2364: (apr_err=160029)
> svn: Commit succeeded, deltification failed
> subversion/libsvn_fs/bdb/bdb-err.c:61: (apr_err=160029)
> svn: Berkeley DB error while deleting string for filesystem
> /home/csd/tmp/repo/db:
> Cannot allocate memory
>
>
> Note that it didn't look like it had really run out of memory but to
> be sure I added 4GB to my swap space and reran the test and I still
> got the same result. It happened at the same point that the first
> one did (i.e. doing the merge of the 2nd imported tree)
If you are able to do so, I'd love to hear if upgrading to Subversion
r5147 or later solves this probelm for you.
Here's what I did:
Stop performing deltification as part of one big whoppin' Berkeley
transaction.
* subversion/libsvn_fs/tree.c
(struct txn_deltify_args, txn_body_txn_deltify): New.
(deltify_mutable): Was deltify_if_mutable_under_txn_id(), and hack
this thing up so that it no longer uses a single trail for the
whole deltification process.
(txn_body_deltify_committed): Remove.
(svn_fs_commit_txn): Use the new and improved deltify_mutable().
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 28 06:37:21 2003