Vidalia not-responding after minute of working
I'm having strange problems with Vidalia in Windows. Before the main problem there were errors while connecting to TOR like client only. When I pushed Start Tor Vidalia started Tor but displayed this process incorrectly. When TOR was already connected and check.torproject.org worked fine Vidalia still displayed yellow "connecting" onion instead of green one, it became green by the time, long after TOR had begun really working. Network map displayed node list, but not my circuits. Message log was also not fine. After displaying message "bootstapped 100%" there were messages like "we have 0/1800 descriptors", "we have 100/1800 descriptors" and so on. When I interrupted connecting by pushing "Stop Tor" Vidalia displayed message box
"Vidalia was unable to register for some events. Many of Vidalia's features may be unavailable.
Control socket is not connected."
These strange things began some weeks ago and happened with Vidalia bundle version 0.2.2.35-0.2.15 and after update to 0.2.2.37-0.2.19. Main, much stranger problem begun when I tried running a non-exit TOR relay. I upgraded Vidalia bundle to version 0.2.2.38-0.2.20. At first it succeded and no problems happened but next time troubles begun. Vidalia started TOR and relay but in a minute or so Vidalia windows became completely white (blank) and not-responding, Vidalia's green onion in taskbar ignored right mouse clicks, while TOR itself continued working and check.torproject.org worked fine. It continued happening when I switched to client only. Then I tried installing older Vidalia bundle versions (0.2.2.35-0.2.15 and 0.2.2.37-0.2.19) all the same. Now I'm writing using TOR from other Windows machine and all works fine. I suspect attack though political regime in my country isn't supposed to be so oppressive as in China.
Trac:
Username: HavingError12