[SVN-2430] Broken repository can kill server

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: all
• Fix Version/s: unscheduled
• Component/s: libsvn_fs_base
• Assignee: Unassigned
• Reporter: Marius Gedminas
• Created: 01/Nov/05 12:27
• Updated: 27/Oct/18 16:33
• Resolved: 10/Nov/07 08:33

Description

I have a SVN repository (bsddb) that I can no longer use -- 'svn up' in a
working directory causes svnserve to eat over 2 gigs of RAM+swap until the
kernel's OOM killer kills it.  'svnadmin dump' has the same problem.  I have
described the problem in greater detail in the mailing list more than a week
ago, but I have received no answers so far.  Here's the archived message:

  http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=40012

http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=40012

Issue Links

• duplicates: SVN-2751 Directory prop mods reverted in overlapping commits scenario.