Last Comment Bug 1313176 - support index/cursor operations on stored WebAssembly modules
: support index/cursor operations on stored WebAssembly modules
Status: NEW
Product: Core
Classification: Components
Component: DOM: IndexedDB (show other bugs)
: Trunk
: Unspecified Unspecified
: P3 normal with 1 vote (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Hsin-Yi Tsai [:hsinyi]
: 1319693 (view as bug list)
Depends on: 1311466
Blocks: 1276029
  Show dependency treegraph
Reported: 2016-10-26 13:04 PDT by Luke Wagner [:luke]
Modified: 2017-01-06 11:59 PST (History)
4 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description User image Luke Wagner [:luke] 2016-10-26 13:04:02 PDT
According to bug 1311466 comment 12: objectStore.getAll(), index.get(), index.getAll() and cursors

I also noticed this will fix an assertion failure in the hidden-by-default devtools Storage pane when attempting to explore an object store containing a wasm module.
Comment 1 User image Andrew Overholt [:overholt] 2016-11-29 12:48:13 PST
*** Bug 1319693 has been marked as a duplicate of this bug. ***
Comment 2 User image Julien Cristau [:jcristau] 2016-11-30 02:34:02 PST
tracking for 52 as that was requested in bug 1319693
Comment 3 User image Benjamin Bouvier [:bbouvier] 2017-01-05 01:55:12 PST
Gentle ping about this: as stated in bug 1319693 comment 0, it's an easy way to crash the browser (especially since emscripten will try to cache wasm modules by default, iiuc): store a wasm module in idb, open devtools and look at the wasm module in idb.

Implementing the full feature might take some time, but maybe we can mitigate the crash in the time being in 52 (target for wasm release) by just failing softly?
Comment 4 User image Luke Wagner [:luke] 2017-01-06 11:59:00 PST
(Oops, just noticed I forgot to CC relevant people on this initially.)

Note You need to log in before you can comment on or make changes to this bug.