Tor sends a badly formatted string through the controlport
While testing the new combination of stable things that conform TBB we found that Vidalia sees the following and freezes waiting for the right string:
Jun 06 23:41:37.778 [debug] QtDebugMsg: torcontrol: Control Reply: BO TSTRAP PROGRESS=54 TAG=loading_descriptors SUMMARY="Loading relay descriptors"650 NOTICE I learned some more directory information, but not enough to build a circuit: We have only 96/2784 usable descriptors. 650 STREAM 81 CLOSED 25 184.108.40.206.$4186509C707E96B77B51A76F8294D7E22FF52C61.exit:443 REASON=END REMOTE_REASON=DONE
This might be a problem with Vidalia's parsing, but it seems that tor concatenates a control event after a control reply without the proper separation.