Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#9382 closed defect (fixed)

Crash in Tor on Windows

Reported by: badadim Owned by:
Priority: Medium Milestone: Tor: 0.2.4.x-final
Component: Core Tor/Tor Version: Tor: 0.2.4.12-alpha
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Faulting application name: tor.exe, version: 0.0.0.0, time stamp: 0x5177f094
Faulting module name: tor.exe, version: 0.0.0.0, time stamp: 0x5177f094
Exception code: 0x40000015
Fault offset: 0x00064e01
Faulting process id: 0x160c
Faulting application start time: 0x01ce8fc9235599b0
Faulting application path: C:\Users\Public\Tor Browser\App\tor.exe
Faulting module path: C:\Users\Public\Tor Browser\App\tor.exe
Report Id: 94073d30-fbbc-11e2-87ca-90fba62c9f2a

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: tor.exe
P2: 0.0.0.0
P3: 5177f094
P4: tor.exe
P5: 0.0.0.0
P6: 5177f094
P7: 40000015
P8: 00064e01
P9:
P10:

Analysis symbol:
Rechecking for solution: 0
Report Id: 94073d30-fbbc-11e2-87ca-90fba62c9f2a
Report Status: 0

Child Tickets

Attachments (5)

Report.wer (7.4 KB) - added by badadim 6 years ago.
Report.2.wer (7.4 KB) - added by badadim 6 years ago.
Report.3.wer (7.9 KB) - added by badadim 6 years ago.
Report.4.wer (7.9 KB) - added by badadim 6 years ago.
Report.5.wer (7.8 KB) - added by badadim 6 years ago.

Download all attachments as: .zip

Change History (13)

Changed 6 years ago by badadim

Attachment: Report.wer added

Changed 6 years ago by badadim

Attachment: Report.2.wer added

Changed 6 years ago by badadim

Attachment: Report.3.wer added

Changed 6 years ago by badadim

Attachment: Report.4.wer added

Changed 6 years ago by badadim

Attachment: Report.5.wer added

comment:1 Changed 6 years ago by badadim

Component: - Select a componentTor
Version: Tor: 0.2.4.12-alpha

comment:2 Changed 6 years ago by nickm

Milestone: Tor: 0.2.4.x-final
Status: newneeds_information
Summary: tor failsCrash in Tor on Windows

Does anybody know how how to interpret these .wer files?

Does this crash occur at startup, or after a while?

Is there anything interesting near the end of the logs?

comment:3 Changed 6 years ago by badadim

Status: needs_informationnew

Hope the below provided helps -

Windows Error Reporting (WER) is a set of Windows technologies that capture software crash data and support end-user reporting of crash information. Through WinQual services, software and hardware vendors can access reports in order to analyze and respond to these problems.

Crash occurs at start up.

Nothing interesting at log files:

Warning Proxy Client: unable to connect to xxxx:54542 ("server rejected con...
Notice: We now have enough directory information to build circuits.
Notice: Bootstrapped 80% Connecting to the Tor network.
Notice: Bootstrapped 90% Establishing a Tor circuit.

as a next step Tor is crashing what generates Report.wer file (other wer files are attached only fyi as they are generated prior to this crash) and Vidalia is not responding. Btw: this is pluggable package installation from tor-pluggable-transports-browser-2.4.12-alpha-2-pt1_en-US.exe

comment:4 Changed 6 years ago by arma

Could this be #9288?

You might try grabbing the tor.exe from the more recent TBB alpha bundle, and popping that into your PT TBB. At least until somebody makes an up-to-date PT TBB.

comment:5 Changed 6 years ago by lance

I don't have access to something that would allow me to view the .wer files, can anyone put them in plaintext or something?

comment:6 in reply to:  description Changed 6 years ago by cypherpunks

Resolution: fixed
Status: newclosed

Exception code: 0x40000015
Fault offset: 0x00064e01

It's from:

  } else if (!strcmpstart(question, "md/id/")) {
    const node_t *node = node_get_by_hex_id(question+strlen("md/id/"));
    const microdesc_t *md = NULL;
    if (node) md = node->md;
    if (md) {
      tor_assert(md->body);

Exception code is STATUS_FATAL_APP_EXIT happened because abort for triggered assert. Fault offset points just to next instruction after "call abort".

This assert should be readable in vidalia's message log, but for some reason it wasn't reported.

Code was already fixed:
https://gitweb.torproject.org/tor.git/commitdiff/e602c4031b57f0780661ce0473a5e30d187d385c

Last edited 6 years ago by cypherpunks (previous) (diff)

comment:7 Changed 6 years ago by nickm

Thanks for tracking this down. How did you do it?

comment:8 Changed 6 years ago by cypherpunks

How did you do it?

Fault offset is RVA. Using disassembler to reading assembler code around this address it's possible to find this part in source code.

Note: See TracTickets for help on using tickets.