Whenever I start tbb-firefox.exe (whether through Vidalia or the .exe itself), it instantly crashes and prompts me with "tbb-firefox.exe has stopped working". This didn't happen in previous releases.
I just confirmed that I can run the latest version of firefox just fine, but from what I understand that isn't the version included in the TBB anyway. If someone can point me to a download of the (unpatched?) version that TBB is using I can try that, too.
I tried both tor-browser-2.3.25-14_en-US.exe and tor-browser-2.3.25-14_de.exe multiple times without success.
I updated my graphics driver because Mozilla had something in their FAQs about old drivers causing potential crashes, but it didn't help. Any other things I should specifically looking out for?
It's PR_NewTCPSocketPair, just entry point of it, which called by PR_NewPollableEvent. Not so much information to get why crashed. Need to know exception code, usually windows reports it for terminated apps.
There's more technical information but I can't seem to copy that out of the error message... The exception code is 0xc0000005 though. Problems with RAM, for all I remember, but that happens even after rebooting my computer.
Can you try to run previous releases of TBB again for test?
What antivirus used? Can you turn it off for test?
If someone can point me to a download of the (unpatched?) version that TBB is using I can try that, too.
It's firefox 17.0.10. Official Firefox binaries builded using another compiler (MSVC), so with the same source code it can lead to different bugs if any exist. But you can to try 17.0.10esr (en-US)
When I tried TBB3.0b1_en-US, tor.exe crashed and I seemed to be unable to get any logs from it, even when editing the torrc. I was unable to start any of the 3.0 alphas, but I guess they're called 'alpha' for a reason.
PR_OpenTCPSocket of nspr4.dll is known as usual target for hooking by various malware/software. Usually it replaces a prologue of target function with the JMP rel32 (E9 opcode) so code of next function shouldn't to be affected, except this case it seems. If JMP d,[addr] (FF25 opcode, 6 bytes) or something another used then code at 12B2 was modified and crash as result.
Browser from tor-browser-2.3.25-8_en-US.exe was compiled with optimizations so code of PR_OpenTCPSocket looks like:
Maybe try disabling hardware acceleration. Go to the Options menu, then click the Advanced tab. Uncheck the box that says "Use hardware acceleration, when available". I had the same issue with an older TBB (can't remember which one), and doing this fixed it. I haven't tested 2.3. On 4.0.2, this is still a problem, but that could be a separate bug. I'm on Windows 7 64-bit.
--New cypherpunk, commenting on this ticket for the first time