1423614 - window.caches methods throwing NS_ERROR_FAILURE on Firefox 57 under https

Status: RESOLVED INACTIVE

(Core :: DOM: Service Workers, defect, P2)

Description

[richard.goater27]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171129230227

Steps to reproduce:

Attempted to use any window.caches method such as `keys` or `has` on apparently any https site.

This example runs in Chrome but does not run for me in Firefox 57: https://googlechrome.github.io/samples/service-worker/window-caches/index.html


Actual results:

Receiving this exception in the rejected promise:
```
columnNumber: 0
data: null
filename: ""
lineNumber: 0
message: ""
name: "NS_ERROR_FAILURE"
result: 2147500037
stack: ""
```


Expected results:

The promise should resolve.

Comment 1

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Hi Eden, pleae help take a look at this!

Comment 2

[Eden Chuang[:edenchuang]]

I will take a look later.

Comment 3

[richard.goater27]

Hi, thanks for processing my ticket. I think this is actually a support issue as I'm fairly certain that it's a permissions problem in my profile folder. Should I reopen this somewhere else to get help with a solution?

Comment 4

[Eden Chuang[:edenchuang]]

Sorry, I can not reproduce your problem, even I modified my profile folder permission.
Because NS_ERROR_FAILURE is too general to hard to realize what situation get into in your case.   
Would you mind to provide more information for debugging and let us improve the error message to be more meaningful?
If you certainly sure that is a permissions problem in your profile folder, what is the permission status of the folder?
If the problem is related to your profile, did you try with a clean profile?

Comment 5

[richard.goater27]

Hi again, sorry for the delay and thanks for attempting to replicate the issue.

I copied this profile from a backup so the folder and most of the files are showing as `rwxrwxrwx`.

I suppose I need to write a script to compare the permissions of common files from another profile and restore them, I guess there isn't an easier way?

Comment 6

[Eden Chuang[:edenchuang]]

This might relate to the enhancement of the bug 1404344.
I will check if could we reproduce with the special DB schema version.

Comment 7

[Marion Daly [:mdaly]]

:janv, want to give this a quick look to see if it's reproducable, if not, close this. Just need to follow Eden's last hunch from comment 6.

Comment 8

[Jan Varga [:janv]]

I would need to get reporter's profile or at least full recursive directory listing to investigate possible problems.
Let me know if that's something you could do.

Comment 9

[richard.goater27]

Attachment: Directory listing of profile

Hi Jan, please see a recursive directory listing attached. Let me know if this isn't what you need or if you need anything more.

Comment 10

[Jan Varga [:janv]]

(In reply to richard.goater27 from comment #9)
> Created attachment 9000198 [details]
> Directory listing of profile
> 
> Hi Jan, please see a recursive directory listing attached. Let me know if
> this isn't what you need or if you need anything more.

Thanks!
Do you also see any error messages in the browser console ?
Anything that mentions: quota, parser, origin, valid, scheme
For example:
Quota 'ftp' is not a valid scheme!: ActorsParent.cpp:8486
Quota Origin 'ftp+++ftp.example.com' failed to parse, handled tokens: : ActorsParent.cpp:8404

or anything that mentions DOM cache or IndexedDB

Comment 11

[richard.goater27]

I can see this in the browser console:

> IndexedDB UnknownErr: ActorsParent.cpp:600

no other details I'm afraid.

Comment 12

[Marion Daly [:mdaly]]

removing NI

Comment 13

[James]

Now the error is fixed for https://comprarporinternet.net/ THANK YOU!!

Comment 14

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

Closing per comment #13. Thanks for reporting back! (WORKSFORME because we don't know when it's fixed and by what)

Comment 15

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

Oh actually wait, that's a spam.

Comment 16

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

(But closing again since this hasn't been reproducible. Sorry for destroying your inbox)