We've been investigating a memory leak in Ripple 1.31 where pods will gradually grow up to 4GB memory use before being killed and restarted by Kubernetes.
I've documented my findings further in the relevant support issue but it seems that this was caused by setting up the RplFormEventBus in a created lifecycle hook rather than mounted. Reverting this caused memory usage to go back down to reasonable levels under sustained load.
I'm not 100% certain of the reasoning behind this change but raising this PR for visibility.
Screenshots
How Has This Been Tested?
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Improvement/refactoring (non-breaking change that doesn't add any features but makes things better)
Checklist
[ ] I've added relevant changes to the documentation.
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] My change requires a template update for create-ripple-app.
[ ] I have added template update script for next release.
Motivation and Context
JIRA issue: https://digital-engagement.atlassian.net/browse/SDPSUP-4751
Changed
We've been investigating a memory leak in Ripple 1.31 where pods will gradually grow up to 4GB memory use before being killed and restarted by Kubernetes.
I've documented my findings further in the relevant support issue but it seems that this was caused by setting up the RplFormEventBus in a
createdlifecycle hook rather thanmounted. Reverting this caused memory usage to go back down to reasonable levels under sustained load.I'm not 100% certain of the reasoning behind this change but raising this PR for visibility.
Screenshots
How Has This Been Tested?
Types of changes
Checklist