Remove support for de-serializing WebAssembly.Modules in IDB
Categories
(Core :: Storage: IndexedDB, task, P2)
Tracking
()
People
(Reporter: janv, Assigned: janv)
References
Details
(Keywords: dev-doc-needed, site-compat)
Attachments
(1 file)
We can just return plain JS objects instead of de-serializing wasm modules.
| Assignee | ||
Comment 1•6 years ago
|
||
Actually, most of the code for preprocessing of WASM modules can be recycled. De-serialization of big structured clones can be more efficient using preprocessing. Big structured clones are currently stored as separate files, but during de-serialization they are fully read in the parent and content is then sent to the child. We can just send them as blobs instead.
My plan is to convert existing code instead of removing it and then adding back. However, I want to keep this feature behind a pref for now.
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 2•6 years ago
|
||
| Assignee | ||
Comment 3•6 years ago
|
||
This patch removes support for de-serialization of WebAssembly.Modules. The
preprocessing which was added just for WebAssembly.Modules is not removed since
it can be reused for more efficient de-serialization of big structured clones
which are stored as standalone files. (standalone files can be read and
uncompressed in content process instead of the parent process). So this patch
also adjusts the preprocessing to support that. However the preprocessing is not
fully implemented (we lack support for indexes and cursors) and there's a
theoretical problem with ordering of IDB requests when preprocessing is
involved, so this feature is kept behind a pref for now.
Comment 5•6 years ago
|
||
| bugherder | ||
Updated•6 years ago
|
Comment 6•6 years ago
|
||
Posted site compatibility note: https://www.fxsitecompat.dev/en-CA/docs/2019/indexeddb-de-serialization-support-has-been-removed-from-webassembly-module/
Updated•6 years ago
|
Description
•