Closed
Bug 1897468
Opened 1 month ago
Closed 1 month ago
Stop non-parent processes from doing anything when recieving a signal.
Categories
(Core :: Gecko Profiler, task)
Core
Gecko Profiler
Tracking
()
RESOLVED
FIXED
128 Branch
Tracking | Status | |
---|---|---|
firefox128 | --- | fixed |
People
(Reporter: aabh, Assigned: aabh)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Currently child processes cannot do anything when receiving a signal, due to sandboxing (they can't write to files, and there's no point starting the profiler for one process if we cannot write the results). Therefore, we should check whether or not we're the child process or not before doing anything when we receive a signal, and do nothing (instead of doing invalid operations) when we get a signal.
Assignee | ||
Comment 1•1 month ago
|
||
Pushed by abrouwersharries@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/2620c322ebed Add checks for whether the profiler is running in a child or parent process when recieving a signal r=canaltinova,profiler-reviewers
Comment 3•1 month ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 month ago
status-firefox128:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•