Perform an audit of existing memory leaks in MR Diffs app
Topic
The MR Diffs app seems to grow significantly in amount of memory used as the user interacts with the app.
With the goal of improving memory footprint of very large MRs (OKR FY21Q2: gitlab-com/www-gitlab-com#7665), we need to first investigate what are the places where this growth is happening due to memory leaks.
Tasks
-
Read https://vuejs.org/v2/cookbook/avoiding-memory-leaks.html -
Discuss approach to identify memory leaks in our app with the team -
Check the app for memory leaks -
Create an issue to implement potential fixes -
Set weight on implementation issue -
If weight is greater than 5, break issue into smaller issues (potentially one per source of the problem)
Risks and Implementation Considerations
Identifying memory leaks in such a large app by profiling is going to be challenging and might yield few hints.
Consider combing patterns of leakage where things are setup but not cleaned up on teardown/destroy.
Edited by André Luís