Closed
Bug 1385274
Opened 7 years ago
Closed 7 years ago
WebAuthnManager asserts when trying to resolve mPBackgroundCreationPromise twice
Categories
(Core :: DOM: Device Interfaces, enhancement)
Core
DOM: Device Interfaces
Tracking
()
RESOLVED
FIXED
mozilla56
Tracking | Status | |
---|---|---|
firefox56 | --- | fixed |
People
(Reporter: ttaubert, Assigned: ttaubert)
References
Details
(Whiteboard: [webauthn])
Attachments
(1 file, 1 obsolete file)
3.45 KB,
patch
|
jcj
:
review+
|
Details | Diff | Splinter Review |
Calling WebAuthnManager::GetOrCreateBackgroundActor() twice in a row (i.e. hitting the button on the test page like a maniac) can cause us to call mPBackgroundCreationPromise.Resolve() twice in a row, without an .Ensure() call in between that would refill mPromise. And thus we assert.
As soon as we filled WebAuthnManager::mChild and it sticks around we actually don't need to create another WebAuthnTransactionChild. And we also don't always need to fire a BackgroundChild runnable.
Assignee | ||
Comment 1•7 years ago
|
||
This seems closer to the pattern other PBackground consumers use. And we don't assert anymore.
Attachment #8891345 -
Flags: review?(jjones)
Assignee | ||
Comment 2•7 years ago
|
||
Some more cleanup.
Attachment #8891345 -
Attachment is obsolete: true
Attachment #8891345 -
Flags: review?(jjones)
Attachment #8891351 -
Flags: review?(jjones)
Updated•7 years ago
|
Attachment #8891351 -
Flags: review?(jjones) → review+
Pushed by ttaubert@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/ee929726e093
Don't try to resolve WebAuthnManager::mPBackgroundCreationPromise twice r=jcj
Comment 4•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox56:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
You need to log in
before you can comment on or make changes to this bug.
Description
•