1269026 - Firefox profiles possibly causing IndexedDB InvalidStateError when opening database

Status: RESOLVED INCOMPLETE

(Core :: Storage: IndexedDB, defect, P5)

Description

[jasonpang2011]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36

Steps to reproduce:

We found that a large number of one of our clients' users are getting an InvalidStateError around opening our IndexedDB database. I suspect it's possible a buggy Firefox profile is the cause of this, because creating a new Firefox profile fixes the issue for some of our clients that have reported issues with opening IndexedDB.

The InvalidStateError is happening on the call to "indexedDb.open('database_name', 1');"

This error has occurred to about 1 out of every 5 people on their site for a total of around ten thousand times.

I'd hoping to find out what the possible reasons are for an IndexedDB InvalidStateError. A link to the source would be really helpful if someone familiar with this could point out a few tips.

- I think we can rule out Private Browsing Mode. It's unlikely 20% of his users are on Private Browsing Mode. But it's known that Private Browsing Mode causes an InvalidStateError.
- We don't upgrade or delete the database, so the database should not be blocked. We just create the database at version 1 the very first time and use it after.

I've pointed a user to this test: https://jsfiddle.net/v79kfzxx/1/, where he confirmed he wasn't in Private Browsing Mode but the IndexedDB test failed and creating a new profile fixed the issue for him. I just don't think I can ask for his Firefox profile though..

Comment 1

[Lina Butler (ex-Mozilla)]

This might be a dupe of bug 1236557, if the user switches between channels (like Nightly and Release) with the same profile. 20% seems really high for that, though. CCing some knowledgeable platform folks.

Comment 2

[jasonpang2011]

Could anybody point out other possible reasons for IndexedDB's InvalidStateError? As Kit mentioned above, it doesn't seem likely that even 1/10th of Firefox users would switch between Firefox versions. If we can single out Private Browsing Mode and IndexedDB upgrade/deletion (both of which I strongly believe are not the case), what possible causes remain?

Comment 3

[Ben Kelly [:bkelly, not reviewing]]

This code search shows where IDB uses this error:

  https://dxr.mozilla.org/mozilla-central/search?q=NS_ERROR_DOM_INVALID_STATE_ERR+path%3Adom%2Findexed&redirect=false&case=false

Seems to get thrown for things like trying to use a transaction or object store after they are closed.

Comment 4

[Kagami Rosylight [:saschanaz] (they/them)]

Updated URL for comment #3:

• https://searchfox.org/mozilla-central/search?q=NS_ERROR_DOM_INVALID_STATE_ERR&path=dom%2Findexed&case=false&regexp=false
• https://searchfox.org/mozilla-central/search?q=ThrowInvalidStateError&path=dom%2FindexedDB&case=true&regexp=false

Comment 5

[Jens Stutte [:jstutte]]

Please file a new report if you still see issues. Thank you for your support!

Comment 6

[Jan Varga [:janv]]

Also:
https://searchfox.org/mozilla-central/rev/5ff3324fe989a19c6fa5ac5b923089ef4ce2ebb2/dom/base/domerr.msg#61
https://searchfox.org/mozilla-central/search?q=NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR&path=&case=false&regexp=false

It looks like it could be related to missing support for private browsing.