[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Eternal loop in quick_hash

From: Oddvar Kloster <Oddvar.Kloster_at_sintef.no>
Date: Wed, 13 Oct 2010 21:21:37 +0200

> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
> Sent: 13. oktober 2010 19:17
> To: dev_at_tortoisesvn.tigris.org
> Subject: Re: Eternal loop in quick_hash
> On 13.10.2010 15:42, Oddvar Kloster wrote:
> > The latest nightly is acting up on me and freezing frequently. There
> > may be other reasons too, but I’ve traced one cause of a freeze.
> When does it freeze? What commands?
> > If one creates an empty quick_hash and inserts a single element using
> > the iterator range insert method (QuickHash.h, 406), the hash does not
> > grow to more than 1 in capacity, which is then filled. The causes the
> > next find() to stick in an endless loop.
> >
> > I suspect that size() on line 410 should be capacity() instead.
> quick_hash() is only used in the log dialog. Does it freeze there?

Yes, I found the problem when running the log dialog. Since it appears to be related to log caching, I've turned that off for the moment. This helped for most of my working copies.
But I still have problems with my Tsvn WC. I thought it might just be corrupt, but then I just did the following:

- Check out new WC of Tsvn trunk, depth immediates.
The following commands on the WC root seize up:
- Commit
- Show log
- Repo-browser
The following commands work:
- Update
- Check for modifications
- Revision graph (at least it starts getting the history before I kill it)

In my original Tsvn WC, I get the attached error on Check for Modifications.
Debugging indicates that svn enters an eternal loop while trying to work upward to the WC root directory.
Nightly r20293.



To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].

Received on 2010-10-13 21:53:57 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.