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
Setup the server with a large set of data (some resources should atleast 50,000 in number)
Sync the resource data to the client.
Expected behavior
Data should sync and get stored in the database.
Actual behavior
App crashes because of O.O.M.
Screenshots
If applicable, add screenshots to help explain your problem. OOM_crash_log.txt
Smartphone (please complete the following information):
Device: [e.g. Pixel4a emulator]
Android version: [e.g. Settings -> About phone -> Android version]
Build number: [e.g. Settings -> About phone -> Build number]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.
Side note
Instead of downloading all the resources and then inserting them to the database, maybe be we should insert downloaded page before we fetch a new one.
The text was updated successfully, but these errors were encountered:
Describe the bug
Syncing a large number of resources causes OOM issue in the engine.
Component
Core library, SDC library, reference app, or SDC gallery app
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Data should sync and get stored in the database.
Actual behavior
App crashes because of O.O.M.
Screenshots
If applicable, add screenshots to help explain your problem.
OOM_crash_log.txt
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.
Side note
Instead of downloading all the resources and then inserting them to the database, maybe be we should insert downloaded page before we fetch a new one.
The text was updated successfully, but these errors were encountered: