Problems with memory and app lock

[celciusjj]

Initially there was a problem with synchronizing a lot of data over 100MB, and we decided to build a chunk system which would insert data in parts. This was developed and from the application a cycle was built where an applyRemoteChanges is made with the data of each chunk until finishing, but sometimes and on some cell phones the memory fills up, and blocks the application, forcing the application to be closed manually since you can't do anything with it.

Any idea why the application is blocking memory, knowing that writing is done in fragments?

updated:
I did a profiling and the memory seemed to be fine, I used an emulator with very high memory and high heap, and the application still crashes. I think that could be a cpu problem.

Profiling cpu, death point is the red circle

The memory increases gradually, the death point is the red circle.

The blocking happens on the following line. Which is inside a loop executing sequentially per fragment

        await database.write(() =>
          applyRemoteChanges(changes, {
            db: database,
            sendCreatedAsUpdated: false,
          }),
        );

complete loop

      for await (const url of map) {
        const data = await fetch(url);
        const response = await data.json();
        const { changes, timestamp } = response;

        await database.write(() =>
          applyRemoteChanges(changes, {
            db: database,
            sendCreatedAsUpdated: false,
          }),
        );

        counter--;
        setUrlsSize(counter);
        await setLastPulledAt(database, timestamp);
      }