[SVN-1224] svn update crashes with "Cannot allocate memory"

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: all
• Fix Version/s: unscheduled
• Component/s: libsvn_fs_base
• Labels: scalability

Environment

Linux

• Assignee: Unassigned
• Reporter: Subversion Importer
• Created: 05/Apr/03 04:04
• Updated: 27/Oct/18 16:38
• Resolved: 05/Oct/05 16:48

Description

I have seen this several times from svn_load_dirs.  When I have a particularly 
large changeset coming in, say 250 files modified or more and a total patch 
size of 15MB or more, when svn_load_dirs does its svn update after applying 
things, I get: 
 
/home/jgoerzen/svn_load_dirs/upstream/svn_load_dirs.pl: /usr/bin/svn 
update failed with this output: 
svn: Berkeley DB error 
svn: Berkeley DB error while reading node revision for filesystem 
/home/jgoerzen/repos/kernel/db: 
Cannot allocate memory 
 
Strangely, clearing out my working directory and running svn co on it directly 
makes things work fine.

Original issue reported by jgoerzen