Actually this is unneeded - IDB writes blobs to files anyways. Would be maybe an optimization? AS we don't need to move memory from renderr to browser, just to write to file, as we know we will for IDB?

The reading from file handle is more important here.

Although, if we want the run-path of WASM to be the same for both idb-saved modules and regular modules, then it would be better to allow direct-to-file blob saving. Esp if things are really big?

In that case they probably should be saved to blob directly from the network, which actually already exists. So maybe not necessary still from the construction point of view?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As mentioned in #2 unclear if this is actually something we want, but leaving available for now anyway. If we do want mmap-able blobs for non-idb backed blobs we'll likely need something like this after all.