Bug: outgoing relay cell sent from src/or/relay.c:836 has n_chan==NULL.

Got the following warn msg while browsing,

[warn] circuit_package_relay_cell(): Bug: outgoing relay cell sent from src/or/relay.c:836 has n_chan==NULL. Dropping. (on Tor 0.3.1.4-alpha fab91a290ded3e74)

changed milestone to %Tor: 0.3.3.x-final

added 031-backport annoyance component::core tor/tor harmless? milestone::Tor: 0.3.3.x-final priority::high resolution::duplicate severity::normal status::closed type::defect version::tor 0.3.1.5-alpha labels

Trac:
Milestone: N/A to Tor: 0.3.2.x-final
Priority: Medium to High

Got (again) the exact same [warn] messages 5 times right before a

Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 355 buildtimes.

Not sure if this was due to that, anyway the [warn] message said,

[warn] circuit_package_relay_cell(): Bug: outgoing relay cell sent from src/or/relay.c:836 has n_chan==NULL. Dropping. (on Tor 0.3.1.5-alpha 83389502ee631465)

So I'm putting Tor 0.3.1.5-alpha as the version.

Trac:
Version: Tor: 0.3.1.4-alpha to Tor: 0.3.1.5-alpha

Hm. I didn't see an obvious cause here, so I've added some stack traces to those warnings with 9c404602a0a5dd, which should appear in future releases of 0.3.1 and 0.3.2. If you get any stack traces here, please paste them on this ticket.

For what it's worth, this bug is probably harmless, but it sure is annoying, and we should fix it anyway.

Trac:
Keywords: N/A deleted, 031-backport harmless? annoyance added

Trac:
Milestone: Tor: 0.3.2.x-final to Tor: 0.3.3.x-final

Same bug as #19711 (moved)?

Replying to arma:

Same bug as #19711 (moved)? Seems this bug's fossil records go back to 0.2.4.x days ;) see #8185 (moved)

Duplicate #8185 (moved)

Trac:
Status: new to closed
Resolution: N/A to duplicate

closed

moved to tpo/core/tor#23105 (closed)