Chris AtLee wrote:
> Hello,
>
> Sorry if this is a duplicate post, I sent this message yesterday and
> didn't see it appear in the mailing list archives, so I figured I'd
> subscribe and try again.
>
> I can semi-reliably reproduce a crash with svn 1.4.0 if I interrupt it
> soon after starting a 'svn status' command. It seems to only crash if I
> interrupt it before any output has been generated (while it's locking
> the wc?) My working copy is fairly large (a few hundred megs), so there
> is often a few seconds before any status information is output. It runs
> clean under valgrind except for an "Invalid read of size 4" at
> apr_hash.c:117, which isn't too surprising.
>
> Please let me know if there's any other information I can make available
> to help track this down.
If I may add some comments about this:
the same crash happens in TortoiseSVN as sent in crashreports indicate.
From what I could gather from the crashreports so far is that the crash
happens when the pool gets cleaned up, and only if the
svn_client_status() call gets interrupted by the cancel callback.
It happens almost every time if I set the cancel flag even before I call
svn_client_status() (which means the very first cancel callback will
stop the function).
I haven't had the time to look closer at this issue though - I know I
should have since about 80% of the crashreports coming in for version
1.4.0 are about this issue.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 5 21:50:11 2006