Opened 7 years ago

Closed 6 years ago

#6448 closed defect (invalid)

mp_pool_release: Assertion chunk->magic

Reported by: torland Owned by:
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.3.17-beta
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

One of my nodes died with this error:

ul 22 22:53:04.000 [err] mp_pool_release(): Bug: mempool.c:299: mp_pool_release: Assertion chunk->magic == 0x09870123 failed; aborting.

Child Tickets

Change History (9)

comment:1 Changed 7 years ago by asn

Priority: normalmajor

Do you have any more info that could be useful for debugging this issue?

Were there any interesting logs above the one you pasted? Has this bug occured more than once? Which version of Tor are you running?

comment:2 Changed 7 years ago by nickm

Milestone: Tor: 0.2.3.x-final

Exciting. This means memory corruption, or bad memory, or something.

These pools are only used for fixed-sized packed relay cells, so that's a place to look.

Did you manage to get a stack trace?

comment:3 Changed 7 years ago by torland

asn: I don't have much information. I see several messages like

Jul 22 21:31:01 torland3 kernel: [4508301.111616] eth0: too many iterations (6) in nv_nic_irq.

and regularily messages

Jul 22 21:48:13 torland3 kernel: [4509332.786186] TCP: Treason uncloaked! Peer 85.242.201.237:52153/443 shrinks window 751954598:751960014. Repaired.

Thats all.

nickm: unfortunately I did not have a stack trace. This happened once and it did not create a core.

comment:4 Changed 7 years ago by nickm

Status: newneeds_information

hm. I don't think that's enough information to track this down. None of those messages relate the crash here. Did it ever happen again?

comment:5 Changed 7 years ago by torland

Unfortunately not. In the meantime I updated the nodes to 0.2.3.19-rc.

comment:6 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:7 Changed 7 years ago by nickm

Component: Tor RelayTor

comment:8 Changed 6 years ago by nickm

Milestone: Tor: 0.2.3.x-finalTor: unspecified

Okay, so without more information there, I'm pretty much in the dark. Did this ever happen again?

comment:9 Changed 6 years ago by torland

Resolution: invalid
Status: needs_informationclosed

I don't have more information and will close this ticket

Note: See TracTickets for help on using tickets.