Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-2430

Broken repository can kill server

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Duplicate
    • all
    • unscheduled
    • libsvn_fs_base
    • None

    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

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            mgedmin Marius Gedminas
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment