ljedrz
ljedrz
I'd need to see some more final logs to tell if this was beyond the retry time or if it somehow happened before that deadline.
Closing due to inactivity and no further reports since the last changes to the related code.
Closing, as this log no longer exists in the codebase; please feel free to reopen if you disagree.
This should be fixed by https://github.com/AleoHQ/snarkOS/pull/2168.
@damomine I assume you're not running `--release` for debugging purposes? As for the issue persisting, I'm pretty sure it's some call to `Router::disconnect` that doesn't resolve the address at the...
Thank _you_ for the aid in debugging! If you'd like to test a further fix, please feel free to apply [this commit](https://github.com/AleoHQ/snarkOS/pull/2181/commits/6fc649312793ed20caac55831bd634131a226195), which should hopefully resolve all the remaining cases...
This should already be fixed with the aforementioned PRs.
Closing, as it seems that this has been fixed. Feel free to reopen if the issue resurfaces.
I've considered this too; if the pending fixes for the address resolver issues don't patch the leaks we've been seeing (which they do for me locally), I will be recommending...
Closing, as we've switched to using `jemalloc` by default.