Vidalia crashes upon startup and when subsequently started requests password

[vidalia]

Win XP Pro SP3

Vidalia 0.1.6

Tor 0.1.2.19

Was using Vidalia 0.0.16 which worked well.

Uninstalled that version, and installed 0.1.6.

Upon starting Vidalia, I can see "connected to the TOR network". Within one minute Vidalia crashes, and a Microsoft error report is generated.

If I try to start Vidalia again, it always requests a password -- and even after entering a password it just continues to request a password.

I can see in Task Manager that Tor is still running.

If I end the Tor process in Task Manager and restart Vidalia, Vidalia crashes and the same error report is generated.

If I restart Vidalia without ending the Tor process in Task Manager, Vidalia continues to constantly request a password.

I will attach the Microsoft error reports. They indicate a problem with the file ssleay32.dll.

I will also attach the debug log.

[vidalia]

ErrorJPG

[vidalia]

MicrosoftErrorReport?

[edmanm]

Can you get a debug log?

[vidalia]

The debug file (debug.log) is 4,157,589 bytes. If it is important, please advise how to attach.

[edmanm]

Just attach it to this ticket (I bumped up the maximum attachment size).

[vidalia]

Win XP Pro SP3

Multiple version of Tor incl. latest.

I'm getting this error too, i went back through all Vidalia version to 0.0.16 where the error stops occuring, MS VS.net debugger gives the following offsets, (version dependent):

0.1.7 - 0.1.4
"Unhandled exception at 0x100223a0 in vidalia.exe: 0xC0000005: Access violation writing location 0x3006716c."

0.1.3 - crash-happy, doesn't even need to start tor to crash
"Unhandled exception at 0x6ff44c59 in vidalia.exe: 0xC0000005: Access violation reading location 0x00000011."

0.1.2
"Unhandled exception at 0x100223a0 in vidalia.exe: 0xC0000005: Access violation writing location 0x3006716c."


0.1.1 & 0.1.0 - error offset changes on each run.

0.1.1
Unhandled exception at 0x034223a0 in vidalia.exe: 0xC0000005: Access violation writing location 0x09c6716c.

Unhandled exception at 0x014223a0 in vidalia.exe: 0xC0000005: Access violation writing location 0x03c6716c.

Unhandled exception at 0x014b23a0 in vidalia.exe: 0xC0000005: Access violation writing location 0x03e1716c.

Unhandled exception at 0x02e923a0 in vidalia.exe: 0xC0000005: Access violation writing location 0x08bb716c.

0.1.0
Unhandled exception at 0x034123a0 in vidalia.exe: 0xC0000005: Access violation writing location 0x09c3716c.

Unhandled exception at 0x02f623a0 in vidalia.exe: 0xC0000005: Access violation writing location 0x08e2716c.

Unhandled exception at 0x014a23a0 in vidalia.exe: 0xC0000005: Access violation writing location 0x03de716c.

Seems to be present in Vidalia 0.1.0 - 0.1.7, almost certainly brought in with 0.1.0.0

(ive seen "[Debug] conn_write_callback(): socket 1728 wants to write." and "[Debug] connection_handle_write(): After TLS write of 512: 0 read, 586 written" quite a bit just before a crash, hope that helps)

[edmanm]

Duplicate of ticket #356.

Here's a couple things you can do to help confirm whether the suggested fix in #356 is plausible:

1. Open a command prompt (Start -> Run -> cmd.exe), run echo %PATH%, and paste the result into this ticket
2. Search your hard drive for ssleay32.dll and then paste the full directory names for all results found into this ticket

[vidalia]

edmanm - thanks for keeping an eye on this ticket. This does look like a duplicate of 356 -- sorry I didn't see that. Attached are the results of "echo %PATH%" and the directory names for ssleay32.dll, for your review:

C:\Documents and Settings\Computer>echo %PATH%
C:\PROGRAM FILES\THINKPAD\UTILITIES;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\Sy
stem32\Wbem;C:\WINDOWS\Downloaded Program Files;C:\Program Files\IBM ThinkVantag
e\Client Security Solution;C:\Program Files\Support Tools\;C:\Program Files\ATI
Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\Fire GL 3D Stud
io Max;C:\Program Files\Common Files\Lenovo;C:\Program Files\ThinkPad\ConnectUti
lities;C:\Program Files\QuickTime\QTSystem\

C:\Program Files\FreePOPs
C:\WINDOWS\System32

If the suggested fix in ticket 356 is plausible in my case, kindly explain what I need to do.

[edmanm]

OK. So try renaming each ssleay32.dll file found to ssleay32.dll_. Then try to run Vidalia to see if you get the same crash as before and post your results here.

Afterwards, be sure you rename each ssleay32.dll_ back to the original file name.

[vidalia]

I did as you instructed with the 2 instances of ssleay32.dll, and subsequently Vidalia worked fine, no crash. During the first minute Vidalia.exe was using maximum CPU cycles (~99%), but then calmed down.

Can you suggest a more permanent solution?

[vidalia]

I didn't do as you instructed :) Instead, I grabbed the latest version of SSLeay32.dll I could find and replaced the one in the windows root (C:\WINDOWS) with the newer one. Vidalia (0.1.7) didn't crash or max out the CPU cycles when started.

Latest ssleay32.dll I could find: http://www.deanlee.cn/programming/openssl-for-windows/

[vidalia]

I experienced the same trouble and solved it by supplying a recent SSLeay32.dll. I suggest either . make vidalia compatible with old versions of SSLeay32.dll or . supply a compatible version of SSLeay32.dll with the Installer

This would allow the use of vidalia to people who are not very intimate to a windows system and therefor will do anything like replacing a dll.

[edmanm]

Superseded by ticket #401.