When running BFG that handles network requests on incentivized testnet, we occasionally get OOM errors.
It's important to note a few things:
we run two types of BFG in incentivized testnet: one to handle network requests, and one to only handle queue items and new blocks. This affects the former.
I am unsure where this is coming from, but my hunch is that it is something with handling requests. We start an unbounded number of goroutines, at least one per request, so it's likely something to do with this.
Confirmation
Describe the bug
When running BFG that handles network requests on incentivized testnet, we occasionally get OOM errors.
It's important to note a few things:
we run two types of BFG in incentivized testnet: one to handle network requests, and one to only handle queue items and new blocks. This affects the former.
I am unsure where this is coming from, but my hunch is that it is something with handling requests. We start an unbounded number of goroutines, at least one per request, so it's likely something to do with this.
Let's see if we can reproduce locally somehow.
Expected behaviour
We should avoid OOM errors.
Environment
Version: Operating System: Architecture:
Additional Information
If this happens again, I will paste more info.