Looks like the SVN bindings are involved…
However, you might want to try Trac 0.9.4pre
(from the svn repository: http://svn.edgewall.com/repos/trac/branches/0.9-stable),
as it contains a fix for a memory leak during resync
. It could be that the SVN binding
error was triggered by an out-of-memory condition.
Also, you can try to turn on the debug output while doing resync
(see TracLogging), and detect which changeset XXX brings up the exception.
You can then check with svn log -v -r XXX
if there's anything special
concerning the character encoding of the listed paths.