Closed
Bug 1956369
Opened 29 days ago
Closed 27 days ago
Add a little more logging when SandboxBroker initialization fails
Categories
(Core :: Security: Process Sandboxing, task)
Core
Security: Process Sandboxing
Tracking
()
RESOLVED
FIXED
138 Branch
Tracking | Status | |
---|---|---|
firefox138 | --- | fixed |
People
(Reporter: jld, Assigned: jld)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
A small thing that would be useful for bug 1954000 is, when a SandboxBroker
can't be created, for the log message to include the number of currently allocated brokers. If that number is unexpectedly large, then maybe we have a leak or simply a transiently large number of them (because destruction is delayed until the process finishes exited, as part of bug 1553850). Alternately, if it looks reasonable, then the cause might be something else.
Assignee | ||
Comment 1•29 days ago
|
||
Updated•29 days ago
|
Assignee: nobody → jld
Status: NEW → ASSIGNED
Updated•29 days ago
|
Attachment #9474529 -
Attachment description: Bug 1956369 - Log number of brokers when failing to create one. → Bug 1956369 - Log number of extant `SandboxBroker`s when failing to create one.
Pushed by jedavis@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a81eb380bda0
Log number of extant `SandboxBroker`s when failing to create one. r=gerard-majax
Comment 3•27 days ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 27 days ago
status-firefox138:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•