[SVN-1069] bad 'svn merge' memleak when patching

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: all
• Fix Version/s: 0.19
• Component/s: libsvn_repos
• Labels: scalability

Environment

Linux

• Assignee: Unassigned
• Reporter: Subversion Importer
• Created: 07/Jan/03 21:16
• Updated: 27/Oct/18 16:39
• Resolved: 15/Sep/04 08:43

Description

While running svn merge URL URL on a very large repository, svn
returned an error about "too many open files".  Further investigation
with strace showed that the DB files were open multiple times. 
Running the attached script on my strace output produced the following.

/svnroot/uw/locks/db.lock is open 69 times
/svnroot/uw/db/log.0000000327 is open 69 times
/svnroot/uw/db/representations is open 70 times
/svnroot/uw/db/nodes is open 69 times
/svnroot/uw/db/revisions is open 69 times
/svnroot/uw/db/copies is open 69 times
/svnroot/uw/db/strings is open 71 times
/svnroot/uw/db/transactions is open 71 times
/svnroot/uw/db/changes is open 69 times

Original issue reported by azverkan

Issue Links

• blocks: SVN-1077 svn merge is running out of memory
• depends upon: SVN-688 client tries to open the same repository more than once
• is blocked by: SVN-688 client tries to open the same repository more than once
• is depended upon by: SVN-1077 svn merge is running out of memory