selsta
selsta
> monerod managed to get through 2 failed 'parse transaction from blob' which before was often the trigger to a OOM kill. "parse transaction from blob" is unrelated
@chaserene What about the amount of incoming and outgoing connections before your node "crashed" / got killed for the first time, not afterwards?
@spackle-xmr limiting in / out is currently a theory, it hasn't been confirmed to work yet. >On that topic, can anyone confirm that lowering --max-txpool-weight from the default will cause...
@Boog900 > Ah ok, transactions are periodically re-broadcasted after being in the txpool for too long, so this could still happen if a lot of txs re-broadcasts line up. The...
> sorry, I don't know what you mean. Sorry I mistyped and didn't proofread. I wanted to ask if transactions are typically re-broadcasted within the first 12h of being in...
Should be solved with #8329 merged.
Not yet, I'm not a Windows user myself, but I will ask someone who might look into it.
Related: #8685 From what I can tell it's a dependency issue and it does not show up with official release binaries.
@Gingeropolous definitely not expected behavior. It's unclear from your messages if you also were able to reproduce this issue with just master or the latest release version? I'm not aware...
Should be fixed with #8566