Opened 6 years ago

Closed 5 years ago

#9118 closed defect (wontfix)

Tor crashes while attempting to start in Win7

Reported by: shankar Owned by: erinn
Priority: Medium Milestone:
Component: Applications/Tor bundles/installation Version:
Severity: Keywords: tbb-crash
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

This error message is wrt the version of Tor available for download as on 23 June 2013.

"Start TOR Browser" completes successfully (i.e. all the stuff about connecting to Tor network etc.) but the Tor browser itself crashes on start with following message.

Problem signature:

Problem Event Name: APPCRASH
Application Name: tbb-firefox.exe
Application Version: 17.0.6.4879
Application Timestamp: 518e5d28
Fault Module Name: nvwgf2um.dll
Fault Module Version: 9.18.13.1106
Fault Module Timestamp: 50f9458d
Exception Code: c0000005
Exception Offset: 000f651a
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 16393
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Upon running Tor 0.2.3.25 tor.exe, the following output in CMD window. Unable to proceed.

Jun 23 08:40:18.391 [notice] Configuration file "C:\Users\Aditya\AppData\Roaming
\tor\torrc" not present, using reasonable defaults.
Jun 23 08:40:18.403 [notice] Initialized libevent version 2.0.21-stable using me
thod win32. Good.
Jun 23 08:40:18.403 [notice] Opening Socks listener on 127.0.0.1:9050
Jun 23 08:40:18.000 [notice] No AES engine found; using AES_* functions.
Jun 23 08:40:18.000 [notice] This OpenSSL has a good implementation of counter m
ode; using it.
Jun 23 08:40:19.000 [notice] OpenSSL OpenSSL 1.0.0k 5 Feb 2013 looks like versio
n 0.9.8m or later; I will try SSL_OP to enable renegotiation
Jun 23 08:40:19.000 [notice] Reloaded microdescriptor cache. Found 3563 descrip
tors.
Jun 23 08:40:20.000 [notice] We now have enough directory information to build c
ircuits.
Jun 23 08:40:20.000 [notice] Bootstrapped 80%: Connecting to the Tor network.
Jun 23 08:40:21.000 [notice] Heartbeat: Tor's uptime is 0:00 hours, with 4 circu
its open. I've sent 0 kB and received 0 kB.
Jun 23 08:40:21.000 [notice] Bootstrapped 85%: Finishing handshake with first ho
p.
Jun 23 08:40:22.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Jun 23 08:40:23.000 [notice] Tor has successfully opened a circuit. Looks like c
lient functionality is working.
Jun 23 08:40:23.000 [notice] Bootstrapped 100%: Done.

Child Tickets

Change History (13)

comment:1 Changed 6 years ago by shankar

Version: Tor: unspecifiedTor: 0.2.3.25

comment:2 Changed 6 years ago by shankar

Version: Tor: 0.2.3.25Tor: 0.2.4.12-alpha

Downloaded and ran 2.4.12 alpha; same problem.

comment:3 Changed 6 years ago by shankar

Works with another installation of W7 Home Standard. The failure is with W7 home premium edition.

comment:4 Changed 6 years ago by nickm

Component: TorTorBrowserButton
Owner: set to mikeperry

I'm not so great with windows crashes, but this looks like TBB crashing rather than the Tor component itself. Moving this ticket into the TB component.

comment:5 Changed 6 years ago by gk

Component: TorBrowserButtonTor bundles/installation
Keywords: tbb-crash added
Milestone: TorBrowserBundle 2.3.x-stable
Owner: changed from mikeperry to erinn
Version: Tor: 0.2.4.12-alpha

Very unlikely that Torbutton is involved here. Moving to Tor bundles as it is probably no patch issue either...

comment:6 Changed 6 years ago by rransom

What is nvwgf2um.dll? (I've never heard of it, and I can't tell from the name what it might be.)

comment:7 in reply to:  6 Changed 6 years ago by gk

Status: newneeds_information

Replying to rransom:

What is nvwgf2um.dll? (I've never heard of it, and I can't tell from the name what it might be.)

Nvidia D3D10 drivers. Which seem to have a crash record. See e.g.:

https://bugzilla.mozilla.org/show_bug.cgi?id=823077
https://bugzilla.mozilla.org/show_bug.cgi?id=828911

@shankar: Do Mozilla's Firefox builds work fine for you? Especially the 17.0.6esr which is the base for the Tor Browser you used? You'll find them here for testing (plus the necessary SHA hash values and Mozilla's key to verify that you really downloaded the binaries you wanted):

ftp://ftp.mozilla.org/pub/firefox/releases/

comment:8 Changed 6 years ago by shankar

Chrome and IE work fine. Just downloaded Firefox and will revert.

Shankar

comment:9 Changed 6 years ago by shankar

You are right. I cannot run FF. So I guess whenever FF fixes their NVidia bug this will also work out. Meanwhile I have managed to make Tor work with another PC so all is well.

Thanks all the help.

Shankar

comment:10 in reply to:  9 Changed 6 years ago by gk

Replying to shankar:

You are right. I cannot run FF. So I guess whenever FF fixes their NVidia bug this will also work out.

It would be cool if you could file a bug with your crash details at https://bugzilla.mozilla.org/ as they might not be aware of this particular one (and getting it fixed would benefit the Tor Browser as well). Mentioning that IE and Chrome work flawlessly might be interesting, too :). Thanks!

comment:11 Changed 6 years ago by gk

Status: needs_informationnew

comment:12 Changed 5 years ago by erinn

Keywords: needs-triage added

comment:13 Changed 5 years ago by gk

Keywords: Windows Tor Crash needs-triage removed
Milestone: TorBrowserBundle 2.3.x-stable
Resolution: wontfix
Status: newclosed

We don't ship ESR 17 anymore, closing.

Note: See TracTickets for help on using tickets.