[ Moving to dev@ since earlier replies in the thread moved there.
Please un-Cc users@ from replies. ]
Uroš Jovanović wrote on Tue, 08 Sep 2020 11:31 +0200:
> Hi Daniel,
>
> Not sure what are "relevant pools", I am not really too familiar with SVN :)
>
The C API manages lifetime of various resou
Hi Daniel,
Not sure what are "relevant pools", I am not really too familiar with SVN :)
Attached below is a minimal reproduction case.
It is a C# winforms app with Check and Cancel button (.NET 4.8 with
SharpSvn 1.9 x64 nuget)
You would just need to type in some real svn repo address in Form1.cs
Uroš Jovanović wrote on Mon, 07 Sep 2020 19:25 +0200:
> when using SharpSvn in context of a larger
> application, this would mean the user needs to close the entire application
> because one unmanaged file handle was left alive.
Have you tried clearing the relevant pools?
Could you help debugging
Hello,
Recently I came across this behaviour where if I use the Cancel API to
cancel a long running checkout operation, the process running the SVN code
leaves an open file handle in the .svn\tmp folder inside the working copy.
Initially, I thought it was a SharpSvn (1.9 x64) issue, but I observe
