Opened 14 months ago

Last modified 13 months ago

#25957 needs_information defect

Tor died: Caught signal 11

Reported by: Pine64ARMv8 Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor:
Severity: Normal Keywords: crash, openssl
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by arma)

from tor.log (tor server: devuan 8A00CE9638BDB4686B91F1F0B229DB3F8C9B8415):
Apr 28 00:58:53.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with 9698 circuits open. I've sent 556.38 GB and received 553.75 GB.
Apr 28 00:58:53.000 [notice] Circuit handshake stats since last time: 21677/21677 TAP, 252349/252349 NTor.
Apr 28 00:58:53.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 1 v3 connections, and 16330 v4 connections; and received 36 v1 connections, 8546 v2 connections, 13955 v3 connections, and 12846 v4 connections.
Apr 28 00:58:53.000 [notice] DoS mitigation since startup: 0 circuits rejected, 0 marked addresses. 0 connections closed. 294 single hop clients refused.

============================================================ T= 1524879769
Tor died: Caught signal 11

Child Tickets

Change History (5)

comment:1 Changed 14 months ago by teor

Keywords: crash openssl 033-must added; died Caught signal 11 removed
Status: newneeds_information

Hi, can you tell us what version of OpenSSL tor was compiled with, and what version you have installed?
When Tor starts up, it logs a message containing this information, if the versions are different.

comment:2 Changed 14 months ago by cypherpunks

A SIGSEGV (segmentation fault) is firing in malloc is usually caused by heap corruption. Heap corruption does not cause a segmentation fault, so you would see that only when malloc tries to access there. The problem is that the code that creates the heap corruption could be in any point even far away from where the malloc is called. It is usually the next-block pointer inside the malloc that is changed by your heap corruption to an invalid address, so that when you call malloc an invalid pointer gets dereferenced and you get a segmentation fault.

comment:3 Changed 13 months ago by teor

Keywords: 033-must removed
Milestone: Tor: 0.3.3.x-finalTor: unspecified

We can't make progress on this issue until we have more information

comment:4 Changed 13 months ago by arma

Description: modified (diff)

comment:5 Changed 13 months ago by arma

See also #26311 for what might be a related bug.

Note: See TracTickets for help on using tickets.