report of browser lock up using web Crypto in a ServiceWorker

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
2 years ago
2 years ago

People

(Reporter: bkelly, Assigned: bkelly)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

2 years ago
We were trying to find out why the guardian mobile labs push experiment only targeted chrome recently.  They told us they ran into a browser deadlock when trying to use Crypto in a worker.  We're collecting more details but wanted to get this filed so we had somewhere to put info.

See:

https://twitter.com/_alastair/status/746040158340976641
(Assignee)

Comment 1

2 years ago
They clarified this was an issue when using it in a ServiceWorker.
Summary: report of browser lock up using web Crypto in Worker thread → report of browser lock up using web Crypto in a ServiceWorker
(Assignee)

Updated

2 years ago
Component: Security → DOM: Security
(Assignee)

Comment 2

2 years ago
I think I see the problem.
(Assignee)

Updated

2 years ago
Assignee: nobody → bkelly
Status: NEW → ASSIGNED
What kind of crypto are they using? I can only think of webcrypto, which has been resolved in bug 842818 (landing in 48).
Component: DOM: Security → Security
Any updates here?
Flags: needinfo?(bkelly)
(Assignee)

Comment 5

2 years ago
I believe this was fixed by bug 1281874.  I have not been able to get feedback from the original reporter, though.  Marking closed for now.
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Depends on: 1281874
Flags: needinfo?(bkelly)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.