Audit Memory Leaks

[mountiny]

Coming from here

Background:

Some third party libraries used in App (like RNPerformance or Airship) set up app lifecycle listeners. Failure to cleanup these listeners on React Native instance destruction results in memory leaks (memory was allocated for the listeners but never released). Memory leaks can result in reduced performance and degraded app responsiveness over time.

Problem:

When navigating between OD and ND or reloading the Expensify App, many global listeners leak through RN instance destruction, which degrades app performance.

Solution:

We should:

• Conduct a comprehensive audit of the app to find all the memory leaks we can. This includes profiling the app in different scenarios (reloading, navigating) to pinpoint exactly where leaks occur.
• Implement fixes for each identified issue incrementally.
• (optional) After solving all leaking scenarios, repeat the audit in 6 months to ensure no new memory leaks have been introduced.

Issue Owner

Current Issue Owner: @mateuuszzzzz

[melvin-bot]

Triggered auto assignment to @twisterdotcom (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Current assignee @mjasikowski is eligible for the AutoAssignerNewDotQuality assigner, not assigning anyone new.

[mountiny]

@mjasikowski will help move this ahead @WoLewicki

[mjasikowski]

@WoLewicki I think you could start with running memory profiling across the main flows and we'll gradually expand from there. If you find anything suspicious, I'll create separate issues for these items.

[melvin-bot]

@WoLewicki Huh... This is 4 days overdue. Who can take care of this?

[mjasikowski]

@WoLewicki any progress here? Do you have an ETA for when this can be handled?

[WoLewicki]

I will try to post in the coming days some of the issues I found on simply reloading the application after start-up without further navigation as those should be handled first.