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
Parsing a large Entity List is currently done with JR functionality which always reads the whole instance into an in-memory XML representation. This can lead to OOM exceptions on devices like this A13.
Steps to reproduce the problem
Download a form with a large attached entity list. See an OOM.
Expected behavior
The form is parsed without using up significant memory.
Other information
Values from CSV should go directly into the database without going through the in-memory representation.
The text was updated successfully, but these errors were encountered:
ODK Collect version
v2024.2.1, #6318
Android version
Android 14
Device used
Galaxy A13
Problem description
Parsing a large Entity List is currently done with JR functionality which always reads the whole instance into an in-memory XML representation. This can lead to OOM exceptions on devices like this A13.
Steps to reproduce the problem
Download a form with a large attached entity list. See an OOM.
Expected behavior
The form is parsed without using up significant memory.
Other information
Values from CSV should go directly into the database without going through the in-memory representation.
The text was updated successfully, but these errors were encountered: