Closed jennifer-richards closed 6 years ago
This was happening fairly frequently when I was starting and stopping a peer until I implemented the part of #68 that fixed cleanup of incoming TRP connections. I have not seen it since then. I suspect there was some null pointer condition caused by trying to send updates to a disconnected peer that had been partially cleaned up.
I am closing this without a test - it will be covered by other testing. Reopen if the segfault occurs again.
Encountered a segfault when preparing a community update for a TRP peer: