Closed Bug 1815340 Opened 1 year ago Closed 8 months ago

Investigate memory limits on mobile, and maybe provide an API for removing memory

Categories

(Firefox :: Translations, task, P3)

task

Tracking

()

RESOLVED WONTFIX

People

(Reporter: gregtatum, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

The language models + engine are 25-45mb of memory, and you can load multiple of them in each tab. We should ensure that we are removing them when not needed, as this can hit bad memory pressure limits on mobile.

:jonalmeida added this comment:

Christian made an excellent point offline - this is a significant amount of memory for mobile and having an explicit API for us to free up memory is needed.

The OS gives us warnings from time to time when the app is using a significant amount of memory that affects the OS. This happens often already with browsers, so we would need an API to act on these calls immediately.

Blocks: 1820240
Depends on: 1826718

It looks like we don't have any telemetry about available memory on Android, I filed bug 1826718.

No longer blocks: fx-translation

After some discussion, we realized a separate process will be required (bug 1815339). With a separate process, we can simply kill that process when we run out of memory.

Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.