Hi,
I've experienced the problems described at
http://www.google.com/search?q=subversion+added%2B+apache+crash
<http://www.google.com/search?q=subversion+added%2B+apache+crash&hl=en&hs=y9
r&lr=&client=firefox-a&rls=org.mozilla:en-US:official&filter=0>
&hl=en&hs=y9r&lr=&client=firefox-a&rls=org.mozilla:en-US:official&filter=0
and, as I can't find any further information regarding this problem, I was
wondering if a fix for this problem exists or is in the pipeline.
A brief overview of the problem:
- Create a branch, and do some work in it, including adding new files to the
repository under this branch.
- Commit the new file to the branch multiple times (so that the new file
gets a history)
- After a while, merge this branch back into the trunk in my trunk working
copy. (This causes the file to show added+ as it's attribute, which I think
is where the problem lies)
- When I do a commit into the trunk, the apache server hangs and nobody can
access this or any other repositories hosted by it. The only option is to
manually stop the apache service and start it again.
System information
- Windows Server 2003 hosting apache 2.0.54 for the server
- Windows XP client.
- Both running Subversion 1.2.3 (I'm scared to update this unless I'm
guaranteed it will fix my problem - this is a production system and I can't
risk downtime or repository corruption)
- TortoiseSVN : This problem appears whether I use tortoise to do the
checkin or svn commit on the commandline, so I don't believe it's a tortoise
problem
The apache log shows the same assertion as the poster in that google search,
namely:
Assertion failed: from_root->fs == to_root->fs, file
C:\Home\brane\src\svn\releases\subversion-1.2.3\subversion\libsvn_fs_fs\tree
.c, line 1934
This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.
I hope this is going to the right list - I don't want to be berated like
that other poster. I'd just like the only problem I've ever encountered with
this software to be fixed. I managed to convince a company of 70 developers
to switch to svn from vss, because I couldn't handle that software any more,
and this is the only blemish in an otherwise impeccable experience.
Thanks for any help you guys can provide
Terence
PS. I'm not sure what the volume on this list will be like, so I don't know
if I'll be able to track all replies to me. If you guys would be so good as
to cc me with your comments, I would appreciate it.
Received on Tue Jun 6 11:58:12 2006