Hello.
I have this problem last 2-3 years, and decided to report it.
So the report: sometimes after restoring Project monitor (PM) from tray i get error report in additional window:
---------------------------
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.
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.htmlSubversion 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.6\ext\subversion\subversion\libsvn_wc\wc_db.c'
line 10238: assertion failed (svn_dirent_is_absolute(local_abspath))
---------------------------
Acc. to reaction to similar exception the answer from subversion.apache:
-----------------
The error itself
comes from the Subversion library but there has been a number of cases
where TortoiseSVN is sending an incorrect path to the Subversion library
causing the assertion. At least you should report what you are trying to do
(most important is your working copy path and your repository URL and the
action you try to do).
------------------
So the only folder in PM is the pinter to working copy with path "C:\WorkDir" on local harddrive. Authentication is stored in TSVN. Repository path is "svn://entsrcsrv3/repository". Working copy has sparsed (?) structure - only some of folders inside trunk and some branches are included in it, with sticky depth.
This error report comes 1-3 times a week, and i am unable to get the cases when it crashes, and when - not, so - no recognizable pattern.
The PC goes stantby overnight, and crashes happen independently of wakeup event - sometimes on morning, sometimes - on afternoon, sometimes even several times a day.
Used TSVN: 1.12-1.14.6 (not sure when i got the first crash of this type - maybe the start version is wrong). OS: Windows 10 Pro updated to 22H2.
Is there anything I can do to help to resolve this crash?
Thanks in advance.