Skip to content

Conversation

@hrobeers
Copy link

@hrobeers hrobeers commented Aug 4, 2017

Node memory can get exhausted because of too high mapOrphanTransactions limit and unlimited mapOrphanBlocks size.

Both limits are made configurable.

shshshsh and others added 2 commits August 5, 2017 01:31
There is no reason to store thousands of orphan transactions;
normally an orphan's parents will either be broadcast or
mined reasonably quickly.

This pull drops the maximum number of orphans from 10,000 down
to 100, and adds a command-line option (-maxorphantx) that is
just like -maxorphanblocks to override the default.

Cherry-picked from: ea3c1b0
@sigmike
Copy link
Contributor

sigmike commented Aug 5, 2017

Looks good to me. The block orphans are much less a problem than in Bitcoin because it requires an unique proof of stake to be accepted. But there's no reason the keep all of them forever in memory.

@peerchemist peerchemist merged commit 518aec7 into peercoin:develop Aug 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants