1311058 - Indexed DB throws unknown error on open in FF49

Status: RESOLVED DUPLICATE of bug 1314361

(WebExtensions :: Compatibility, defect)

Description

[chernikov.lesha]

Attachment: instant_translate_select_and_translate-2.9.112-an+fx.xpi

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

Steps to reproduce:

In my extension, I use IndexedDB as a long-term storage.

It was working perfectly in FF48, but starting with FF49 some users (mostly Windows, or even only Windows - not sure) started complaining that it stopped working. After some investigation, I figured out that it was caused by an unknown error on indexed db open. 


Actual results:

Opening an Indexed database fails with an unknown error: "The operation failed for reasons unrelated to the database itself and not covered by any other error code."


Expected results:

Successful database open

Comment 1

[Loic]

After installing your extension, what do I need to do to see the error about IndexedDB?

Comment 2

[chernikov.lesha]

(In reply to Loic from comment #1)
> After installing your extension, what do I need to do to see the error about
> IndexedDB?

Open the pop-up window in the browser toolbar and try to translate something. Bad behaviour is when it hangs with "Loading..." forever—then, there might be errors in the background page (accessible via browser toolbox).

Comment 3

[Loic]

I tested with FF52. Sometimes, when I open the add-on sidebar from the browser toolbar, I got the unresponsive script dialog box:
"A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.

Script: moz-extension://4c1e4f75-8adc-…119e02242460/src/lib/jquery.js:3"

I get some crashes sometimes too.

Is it the issue?

Comment 4

[Loic]

In addition, could you update and attach a version of your extension without strict_min_version (or with a very lower number like 40 instead of 48), it blocks me for testing some old versions of Firefox (I got some corrupt error messages after modifying manifest.json)

Comment 5

[Adrian Florinescu [:aflorinescu]]

I didn't actually test this since Loic is handling that part, but it does seem at this point a compatibility issue. Setting component accordingly.

Comment 6

[Loic]

Chernikov, any update?

Comment 7

[Kris Maglione [:kmag]]

Are you able to reproduce this issue yourself? If so, can you reproduce it consistently?

It would help if we could find a regression range, or see the console output from a debug build, but we need to be able to consistently reproduce to do either of those.

Thanks

Comment 8

[:shell escalante]

can reopen with data requested if needed

Comment 9

[Kris Maglione [:kmag]]

Based on other reports, and the fact that this only happens on Windows, it seems like this is a path length issue brought on by the addition of origin attributes to storage path names.