1458515 - indexedDB writing and reading broken

Status: RESOLVED DUPLICATE of bug 1458320

(WebExtensions :: Storage, defect)

Description

[Martin Giger [:freaktechnik]]

Since yesterday's nightly one of my extensions broke (). Trying to interact with the indexedDB resulted in "bad serialized structured data (incompatible structured clone scope)" Errors. Deleting the existing indexedDB in the storage debugger and re-installing the extension fixed the issue.

The extension calls navigator.sotrageManager.persist() if available, not sure if it was ever called though, since the broken DB was marked as "default" in the storage debugger. That indexedDB is in the moz-extension:// URI.

There is also a persisted indexedDB under indexedDB++++<extensionID>, that I can not delete and appears completely empty (not even object stores).

I haven't tried to reproduce this yet, but I assume it involves some storage migrations.

Comment 1

[Martin Giger [:freaktechnik]]

The extension I meant to mention is https://addons.mozilla.org/en-US/firefox/addon/justintv-stream-notificatio/

Comment 2

[Sebastian Simon]

I experience this with GreaseMonkey 4.3 currently. I can neither access nor store any user-script accross restarts of Nightly.

The console shows errors like:

PushService: stateChangeProcessEnqueue: Error transitioning state AbortError (PushService.jsm:145)
Error: ID already exists: BA:0 (ext-menus.js)
…
bad serialized structured data (incompatible structured clone scope)
InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable (IndexedDB.jsm:31)

I don’t know which ones relate to this recent bug, but they appear new to me.

Comment 3

[Sebastian Simon]

This is possibly a dupe of https://bugzilla.mozilla.org/show_bug.cgi?id=1458320.

Comment 4

[Johann Hofmann [:johannh]]

Very likely, yeah.