Open
Bug 1394990
Opened 8 years ago
Updated 3 years ago
webcrypto: see if we can avoid allocating so much memory when many promises are queued up
Categories
(Core :: DOM: Web Crypto, enhancement, P3)
Core
DOM: Web Crypto
Tracking
()
NEW
People
(Reporter: keeler, Unassigned)
Details
(Whiteboard: [domsecurity-backlog1])
context: bug 1353762
When js running in a content page makes a large number of webcrypto promises, Firefox tends to OOM faster than, for example, Chrome. There may be ways to avoid this. (See in particular bug 1353762 comment 7.)
|
||
Comment 1•8 years ago
|
||
Tim, bug 1353762 was marked critical, how about this one? Can you rate it please.
Flags: needinfo?(ttaubert)
|
||
Comment 2•8 years ago
|
||
I don't think it deserved a critical rating, this one probably doesn't either. It would be nice to have a fix of course.
Flags: needinfo?(ttaubert)
|
|
||
Updated•8 years ago
|
Priority: -- → P3
Whiteboard: [domsecurity-backlog1]
|
||
Updated•6 years ago
|
Component: DOM: Security → DOM: Web Crypto
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•