Out of memory (OOM) warning when loading app with persistence enabled

[michaelAtCoalesce]

Operating System

Mac OS x

Browser Version

Version 114.0.5735.198 (Official Build) (arm64) Automatically update Chrome for all users Learn more

Firebase SDK Version

9.22.0

Firebase SDK Product:

Firestore

Describe your project's tooling

create react app with yarn

Describe the problem

when loading one of the pages of our app that is data intensive with firestore local persistence enabled, when the debugger is open we are seeing a warning about potential OOM.

upon resuming execution, the app does continue to work, but it is concerning that chrome is saying that it's about to run out of memory.

Steps and code to reproduce issue

this occurs in our application when a lot of data is being handled, which makes it somewhat difficult to create a separate reproducible test case.

im happy to jump on a call and try out binaries as needed.

[ehsannas]

Thanks for reporting @michaelAtCoalesce.

When persistence is enabled, the Firestore Web SDK should keep most things on disk, and only load necessary pieces of information into the memory. Note that if you make a query, the entire result set is loaded into memory completely. So, if your application is making queries with a large result set, it could use a lot of memory. Have you considered paginating your results?

[google-oss-bot]

Hey @michaelAtCoalesce. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[dconeybe]

Could this be a symptom of #6118?

[ehsannas]

This issue occurs on Chrome, whereas #6118 seems to be a Safari-only issue (web-channel uses a large amount of memory on Safari).

[dconeybe]

This issue occurs on Chrome, whereas #6118 seems to be a Safari-only issue (web-channel uses a large amount of memory on Safari).

True, although the fact that the customer only experiences the issue on mobile Safari could be a red herring. The investigation in b/242550738 (Googlers only, sorry) seems to be converging on a non-Safari-specific root cause. It's something to keep an eye on anyways.