It's definitely not a unique occurrence. Colleague of mine encountered this too recently. Our repository's working copy size is ~1TB populated with files around 5MB. This exception pops up during cleanup operation (probably after an interrupted update), preventing it from finishing. As the working copy is stuck in locked state, it's no longer usable once this happens and needs to be re-downloaded. Unfortunately I don't have a copy of the corrupted working copy, so I can't provide more details.
On Fri, Oct 2, 2020 at 1:28 AM Ryan Schmidt <subversion-2...@ryandesign.com> wrote: > > > On Oct 1, 2020, at 17:11, Brian Stuart wrote: > > > --------------------------- > > Subversion Exception! > > --------------------------- > > Subversion encountered a serious problem. > > Please take the time to report this on the Subversion mailing list > > with as much information as possible about what > > you were trying to do. > > What were you doing when this happened? > > > But please first search the mailing list archives for the error message > > to avoid reporting the same problem repeatedly. > > You can find the mailing list archives at > > https://subversion.apache.org/mailing-lists.html > > > > Subversion reported the following > > (you can copy the content of this dialog > > to the clipboard using Ctrl-C): > > > > In file > > > 'D:\Development\SVN\Releases\TortoiseSVN-1.14.0\ext\subversion\subversion\libsvn_wc\wc_db.c' > > line 10238: assertion failed (svn_dirent_is_absolute(local_abspath)) > > --------------------------- > > OK > > --------------------------- > > >
