From: Hans-Emil Skogh wrote:
>>> I tried to commit a single file in a working copy using the latest
>>> nightly. (WC on a network share, repo via svn://.) Thi s ended up
>>> hanging the committing TortoiseProc.exe instance, somewhere around
>>> "sending data", with 100% processor usage.
Did it first fail with last Wednesday's build or
already before that?
>>> Then I tried committing the file with the (nightly-build-provided)
>>> command line client. It succeeded.
>> Thanks for the dump file. The stacktrace showed it was inside
>> libsvn_delta\diff.c trying to gather the diff to send. No idea why
>> this would hang with TSVN but succeed with the command line client.
>> That doesn't really make any sense to me.
>
> It has happened for two separate files now. Both in the same WC. Both
> pretty ordinary source files except they are having the svn:eol-style set
> to LF. No idea what could be the cause...
>
>> When you commit from the CL client, are you using absolute paths?
>
>No. I entered the directory in the wc where the file is located and entered something like:
>C:\Some\Path\svn.exe ci -m "Informative message" myfile.ext
I observed a similar issue with last Friday's nightly.
In *that* build, the diff was broken in some cases
(e.g. generating certain uni-diffs between log entries).
But because the problem was gone in the next build,
I did not look into it too deeply.
The code spun over a short sequence of machine
instructions that were r/o, i.e. the that loop would
never be exited. From the looks of it, this seems to
be a compiler bug - possibly caused by the "doubly"
concurrent build of the sln. I kind of remember to
have seen some post about that somewhere but
could not find it again.
-- Stefan^2.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2708681
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-03-01 10:14:35 CET