1944041 - Implement shared memory fallback for large keys and index keys in IndexedDB

Status: RESOLVED WORKSFORME

(Core :: Storage: IndexedDB, enhancement, P3)

Description

[Jan Varga [:janv]]

Currently, if a key or index key is too large, the user receives a "max serialized message size" error because these objects do not automatically fall back to shared memory during serialization. This behavior differs from structured clones, which already use a fallback mechanism for large data (e.g., exceeding 64KB).

To ensure consistency and improve reliability, large keys and index keys should also adopt the shared memory fallback approach to prevent hitting IPC size limits.

Comment 1

[Jan Varga [:janv]]

I spoke with Nika, and IPC already supports this. The only issue arises in cases where there are large arrays with items smaller than 64KB, as this can quickly lead to a 'message too big' crash which seems to be the case in 1943951.