Closed
Bug 1489196
Opened 7 years ago
Closed 7 years ago
Some perf issues with the domain code in ContentPrincipal::Read
Categories
(Core :: Security: CAPS, enhancement)
Core
Security: CAPS
Tracking
()
RESOLVED
FIXED
mozilla64
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | fixed |
People
(Reporter: jandem, Assigned: jandem)
Details
Attachments
(1 file)
Some issues with the SetDomain call in ContentPrincipal::Read:
(1) SetDomain calls SetHasExplicitDomain unconditionally, but Read usually passes a nullptr domain so we unnecessarily deoptimize later checks.
(2) I think we don't need the wrapper recomputation in SetDomain when called from Read because we just created the principal.
I'm Try-servering a patch.
| Assignee | ||
Comment 1•7 years ago
|
||
This fixes two issues:
1) We no longer SetHasExplicitDomain() when the domain is null.
2) We avoid the unnecessary (because new principal) wrapper recomputation.
Comment 2•7 years ago
|
||
Comment on attachment 9006964 [details]
Bug 1489196 - Don't call SetDomain in ContentPrincipal::Read. r?bholley
Bobby Holley (:bholley) has approved the revision.
Attachment #9006964 -
Flags: review+
Pushed by jandemooij@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/50313b936f90
Don't call SetDomain in ContentPrincipal::Read. r=bholley
Comment 4•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in
before you can comment on or make changes to this bug.
Description
•