Closed
Conversation
|
@simedw this will temporarily solve your problem. If you have some availability and appetite to experiment with me on this I'd be happy to try some small stuff with as well. |
Merged
Contributor
|
With updates in V2.0.0 this has been substantially mitigated, based on my testing. I hope it works for others as well. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
We have had an issue for the past few months that agent_manager receives messages faster than it can handle. These messages end up taking more and more memory and eventually BEAM crashes due to out of memory.
This PR allows us to set
max_heap_size, when the heap surpasses this limit the process will be killed (and then restarted by the supervisor).