On 11/27/2015 12:16 PM, Marc Strapetz wrote:
> One of our users is reporting frequent clean up errors:
>
> svn: E720032: Can't remove
> 'C:\Project\Path\To\WorkingCopy\.svn\tmp\svn-30D0973'
> svn: E720032: Can't remove file
> 'C:\Project\Path\To\WorkingCopy\.svn\tmp\svn-30D0973': Det går inte
> att komma åt filen eftersom den används av en annan process.
>
> When investigating file system locks, smartsvn.exe (which is using
> Subversion binaries) is the only process which is holding locks on
> this file. Locks are hold until SmartSVN is closed.
>
> Which parts of the code might hold locks on such temporary files and
> might this be caused by wrong API usage?
>
> As a side note, he is only able to perform a clean up with NetBeans
> (which is using SVNKit), once SmartSVN has been closed. This means,
> that he is also using SVNKit on the same working copy (but not
> necessarily concurrently).
>
First of all: Wrong mailing list. Should go to
users_at_subversion.apache.org (pls reply there).
Which SVN version is being used (client / server)?
Did you check this on the SmartSVN Forums, since you suggest it's a
smartSVN-related issue?
Did you consider a virus scanner issue (aka: a VS keeping the reference
and preventing SmartSVN to release it)?
--
Regards,
Stefan Hett
Received on 2015-11-27 13:47:33 CET