The Indexed DB back end should implement a MemoryPressureListener. On  MEMORY_PRESSURE_LEVEL_CRITICAL we should abort all outstanding write transactions to avoid hitting OOM.

See https://codereview.chromium.org/1953703004 for an example of hooking up DOMStorage to the memory pressure event.

This would likely help scenarios like  issue 533648  and issue 561698 and issue 527995. It's a big hammer but better than crashing, and better than an arbitrary limit on the number of transactions or size of a transaction.

Naively, we'd have the context (per storage partition) listen, and it would abort all outstanding transactions from every back-end (origin) under its control.


 

The Indexed DB back end could implement a MemoryPressureListener and do things to reduce in-memory usage.

See https://codereview.chromium.org/1953703004 for an example of hooking up DOMStorage to the memory pressure event.

This would likely help scenarios like   issue 533648   and  issue 561698  and issue 527995. It's a big hammer but better than crashing, and better than an arbitrary limit on the number of transactions or size of a transaction.