You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Viewing and then exiting a saved form causes a memory leak as the in memory representation of the form is not cleared away on exit.
Steps to reproduce the problem
Finalize a form
Open the form in Ready to Send
Exit the form
The memory usage of the app will increase each time you repeat 2 and 3 (even after garbage collection).
Expected behavior
The memory increase after viewing a form should be cleaned up by garbage collection.
Other information
This happens because when we open a form to view we start ViewOnlyHierarchyActivity and finish FormFillingActivity immediately without calling exit() which cleans up the form session in FormSessionRepository. This means that the FormController (and other form data) are held in memory indefinitely.
We could potentially fix this easily by just clearing the form session when exiting ViewOnlyHierarchyActivity.
The text was updated successfully, but these errors were encountered:
Blocked by #5420ODK Collect version
v2024.3
Problem description
Viewing and then exiting a saved form causes a memory leak as the in memory representation of the form is not cleared away on exit.
Steps to reproduce the problem
The memory usage of the app will increase each time you repeat 2 and 3 (even after garbage collection).
Expected behavior
The memory increase after viewing a form should be cleaned up by garbage collection.
Other information
This happens because when we open a form to view we start
ViewOnlyHierarchyActivity
and finishFormFillingActivity
immediately without callingexit()
which cleans up the form session inFormSessionRepository
. This means that theFormController
(and other form data) are held in memory indefinitely.We could potentially fix this easily by just clearing the form session when exiting
ViewOnlyHierarchyActivity
.The text was updated successfully, but these errors were encountered: