Sign up ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I have a Windows Vista machine that has been connecting to productively for awhile... until recently.

Lately, when I attempt to pull or clone, the update appears to stall...

I see the following messages on the screen when I attempt to clone (with --debug):

sending between command
destination directory: web-main
sending heads command
requesting all changes
sending changegroup command
adding changesets
changesets: 1 chunks
add changeset 203e82b1b502
changesets: 2 chunks
add changeset 746047ca7781
changesets: 3 chunks
changesets: 3407 chunks
add changeset 475299c33a81
changesets: 3408 chunks
add changeset 71fbe52ec211
changesets: 3409 chunks
add changeset edcd21a471b5

And then... nothing happens.

I have opened the Task Manager and there doesn't appear to be any significant network activity for HOURS.

I can contact the server with FireFox and see the proper output.

I can clone from the repo with Solaris and/or Mac OS X... so the issue doesn't appear to be at the 'other end'.

I had been running a fairly old version of Mercurial successfully before this started happening. After it started happening, I upgraded to Mercurial 1.5.2.. which did not help resolve the issue at all.

What are the likely causes and work-arounds for this?

share|improve this question
Was it working before? Do you see anything happening network wise? Have you tried with --debug? – tonfa May 29 '10 at 11:15
Same here, it freezes without any error on Windows Server 2008 SP2 with TortoiseHg 1.0.3 or Mercurial 1.5.4 (at different steps) – alexandrul Jun 1 '10 at 21:24
Have you been able to fix this in the mean time? If so, then please provide an answer below. @alexandrul: did you try asking on the Mercurial mailinglist: – Martin Geisler Dec 25 '11 at 23:20
@MartinGeisler: at this moment it works for me on Windows Server 2008 x64 with hg 1.9.3 – alexandrul Dec 26 '11 at 11:27
@alexandrul: okay, it's good to hear that. So I guess upgrading is the answer here. – Martin Geisler Dec 26 '11 at 12:25

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.