[WebAssembly] Indexeddb structured cloning of WebAssembly is not stable across launch
Reported by
gauravde...@gmail.com,
Oct 3 2017
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.91 Safari/537.36 Steps to reproduce the problem: (1) Unzip worker.zip to a local folder (2) run any server in this directory say http-server -p 8567 (3) Goto localhost:8567/a.html in browser (4) In a new tab open chrome://indexeddb-internals/ to observe (5) Then close the browser (optional) and restart the browser and goto localhost:8567/a.html again and observe the size of indexeddb again What is the expected behavior? Size of indexeddb should remain consistent What went wrong? Size of indexeddb is different on 2 launch for the same webasembly file in chrome://indexeddb-internals/ Launch 1 http://localhost:8567 Size: 8.9 MB Launch 2 http://localhost:8567 Size: 1,998 KB Did this work before? N/A Chrome version: 63.0.3230.0 Channel: canary OS Version: 10.0 Flash Version:
,
Oct 3 2017
Issue 771108 has been merged into this issue.
,
Oct 3 2017
Issue 771109 has been merged into this issue.
,
Oct 3 2017
Is the data present in the database as expected? Chrome's Indexed DB implementation lazily compacts data behind the scenes - discarding old records, moving things between backing files, compressing data, etc., so the size change is entirely expected, especially as reported by the internals inspector. Are you seeing this manifest as problems for your web app?
,
Oct 4 2017
Loading WebAssembly from indexeddb is taking long time in webworker in our webapplication (as much time as if it was actually getting compiled on first launch) But loading it in main thread is not taking that much time.SerializedScriptValueFactory::deserialize() is taking all the time in webworker. While trying to find a shorter repro I found this size issue and other crashes - so thought that they might be related.
,
Oct 4 2017
Thank you for providing more feedback. Adding requester "jsbell@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 4 2017
As there doesn't appear to be a problem with the behavior, resolving as WAI. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by rtoy@chromium.org
, Oct 3 2017