Issue metadata
Sign in to add a comment
|
Caching compiled WASM in indexedDB fails due to DataCloneError
Reported by
jon...@zynga.com,
Jan 18 2018
|
||||||||||||||||||||||||
Issue descriptionVersion: 63.0.3239.132 OS: OSX Architecture: x64 What steps will reproduce the problem? 1. Caching compiled WASM module in indexDB as per https://developer.mozilla.org/en-US/docs/WebAssembly/Caching_modules 2. indexedDB put operation will sometimes fail due to DataCloneError. What is the expected output? Able to properly put compiled WASM module in indexedDB What do you see instead? error thrown on store.put(module, id): DataCloneError: Failed to execute 'put' on 'IDBObjectStore': #<Module> could not be cloned In some test cases we can successfully store the WASM module in the indexedDB, but sometimes it fails with the error above. WASM module is not changed in any way after being being generated via WebAssembly.instantiate() call.
,
Jan 31 2018
I don't think that is yet supported?
,
Jan 31 2018
,
Jan 31 2018
I see this functionality succeed sometimes so I assumed it was supported. However it fails under certain conditions (with DataCloneError) that I'm not yet able to independently reproduce. I've been experimenting with different .js structures in an attempt to work around the error but as yet without success.
,
Jan 31 2018
#4: Is it possible that you had chrome://flags/#enable-webassembly enabled?
,
Jan 31 2018
Thanks for your attention on this issue. Yeah. I had it enabled. Did not realize this was not the default setting. Okay. So it's settled this is not yet supported. I can drop it. However I don't see many specifics about this in the roadmap? Is there any thought to support this functionality in the future? I got the impression was was going to be recommended practice (caching compiled WASM in indexDB) for the medium term.
,
Feb 1 2018
Thank you for the quick response! We're working on getting the WASM support out of the flag. I'll close this as a duplicate of the issue tracking that work, and you can star that issue for updates. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by hablich@chromium.org
, Jan 31 2018