Author: Jonathan Toomim 2015-10-18 15:59:11
Published on: 2015-10-18T15:59:11+00:00
Wladimir J. van der Laan, a bitcoin developer, has reported that some bitcoin mempools are using up to 35GB of RAM, which is much higher than the serialized transaction sizes suggest. It's unlikely this is normal behavior, and it may be related to CreateNewBlock() and getblocktemplate. Valgrind hasn't shown anything suspicious yet. In the meantime, users can mitigate mempool growth by setting -mintxfee.
Updated on: 2023-06-11T00:07:46.864776+00:00