bridge or_conns aren't always setting identity map

Dec 21 05:45:37.909 [warn] connection_or_remove_from_identity_map(): Bug: Didn't find connection '$BD1A1566356ECC9FBF2BB8DE2CEE8C3F39BE61C9' on identity map whe n trying to remove it. Dec 21 05:45:37.909 [warn] connection_or_remove_from_identity_map(): Bug: Didn't find connection '$BD1A1566356ECC9FBF2BB8DE2CEE8C3F39BE61C9' on identity map whe n trying to remove it. Dec 21 05:45:37.910 [warn] _connection_free(): Bug: called on OR conn with non-z eroed identity_digest

I usually get this when I kill my bridge while the bridge user's connection to it is still open.

I used to think it was due to the "unkeyed bridge" concept, where we don't specify a digest and leave the or_conn with a digest of 000..000 for a while at the start.

But now I'm not so sure; I think I've seen this in cases where we specify the digest when configuring the bridge too.

This bug has been around since 0.2.0.7-alpha or so. It appears harmless, but still worth fixing sometime.

[Automatically added by flyspray2trac: Operating System: All]