Opened 6 months ago

Last modified 2 months ago

#33469 needs_information defect

INTERNAL ERROR: Raw assertion failed at src/lib/malloc/map_anon.c:239: lock_result == 0

Reported by: m95d Owned by:
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version: 0.4.2.6
Severity: Normal Keywords: crash, malloc, map_anon, windows, 042-backport
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I tried updating to latest stable version and I have this error after a couple of minutes:

Feb 27 14:38:04.987 [notice] Tor 0.4.2.6 (git-971a6beff5a53434) running on Windows Server 2003 with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Feb 27 14:38:05.003 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Feb 27 14:38:05.018 [notice] Read configuration file "U:\2\Server\TOR\tor.ini".
Feb 27 14:38:05.018 [notice] Based on detected system memory, MaxMemInQueues is set to 2048 MB. You can override this by setting MaxMemInQueues by hand.
Feb 27 14:38:05.034 [warn] You specified a public address '0.0.0.0:8080' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
Feb 27 14:38:05.034 [notice] Opening Socks listener on 0.0.0.0:8080
Feb 27 14:38:05.034 [notice] Opened Socks listener on 0.0.0.0:8080
Feb 27 14:38:05.034 [notice] Opening Control listener on 127.0.0.1:9051
Feb 27 14:38:05.049 [notice] Opened Control listener on 127.0.0.1:9051
Feb 27 14:38:05.049 [notice] Opening OR listener on 0.0.0.0:9001
Feb 27 14:38:05.049 [notice] Opened OR listener on 0.0.0.0:9001
Feb 27 14:38:05.049 [notice] Opening Directory listener on 0.0.0.0:9030
Feb 27 14:38:05.049 [notice] Opened Directory listener on 0.0.0.0:9030

============================================================ T= 1582807176
INTERNAL ERROR: Raw assertion failed in Tor 0.4.2.6 (git-971a6beff5a53434) at src/lib/malloc/map_anon.c:239: lock_result == 0

Child Tickets

Change History (12)

comment:1 Changed 6 months ago by nickm

Keywords: windows 042-backport 043-must added
Milestone: Tor: 0.4.3.x-final
Priority: MediumHigh

comment:2 Changed 6 months ago by gk

FWIW, that came up after I asked an operator to upgrade from 0.2.9.10 [sic!] and they said they could not due to bugs in 0.3.5.x (I suspect #24857 but that's not confirmed yet) and this issue.

comment:3 Changed 5 months ago by nickm

I also suspect that this is related to #24857.

comment:4 in reply to:  3 Changed 5 months ago by gk

Replying to nickm:

I also suspect that this is related to #24857.

Do you mean this bug or the 0.3.5.x issue i mention in comment:2? IIRC they did not test running 0.4.2.6 with DirCache disabled but I could ask if that would be a worthwhile experiment.

comment:5 Changed 5 months ago by nickm

Oh, no -- Sorry, I thought that this bug might be related to #24857, but it probably isn't. I got misled by the word "mmap()".

comment:6 Changed 5 months ago by nickm

For this bug, I'd really like to know what version of windows this is.

comment:7 in reply to:  6 Changed 5 months ago by gk

Replying to nickm:

For this bug, I'd really like to know what version of windows this is.

The relay in question is http://rougmnvswfsmd4dq.onion/rs.html#details/D5D495761788480D0990654F4C4B6E5BD1126A78 and I believe the Windows version did not change for the 0.4.2.6 experiment (m95d: please correct me if I am wrong). Thus, Windows Server 2003.

comment:8 Changed 5 months ago by m95d

Windows server 2003 x64

comment:9 Changed 4 months ago by nickm

Keywords: 043-must removed
Milestone: Tor: 0.4.3.x-finalTor: 0.4.4.x-final

Okay. We should fix this if we can, but if it _only_ affects windows server 2003, then it is not critical for 0.4.3. (MS hasn't supported WS2003 since 2015)

comment:10 Changed 3 months ago by dgoulet

Keywords: crash added

comment:11 Changed 3 months ago by nickm

Keywords: 044-must added

Add 044-must to all crash tickets in 0.4.4

comment:12 Changed 2 months ago by nickm

Keywords: 044-must removed
Milestone: Tor: 0.4.4.x-finalTor: unspecified
Status: newneeds_information

does this affect any supported version of windows?

Note: See TracTickets for help on using tickets.