Closed
Bug 1866465
Opened 2 years ago
Closed 2 years ago
Handle special message types
Categories
(Core :: Fuzzing, enhancement)
Tracking
()
RESOLVED
FIXED
122 Branch
| Tracking | Status | |
|---|---|---|
| firefox122 | --- | fixed |
People
(Reporter: decoder, Assigned: decoder)
Details
Attachments
(1 file)
There are a number of message types that are handled internally in the IPC layer and will never end up as MessageTasks. There is two problems with this:
-
They need special synchronization, otherwise they will cause timeouts (as they will never generate a MessageTask even though the implementation expects one).
-
Some of these messages can cause ports to go away, etc. causing the follow-up messages to be useless, so we should release after sending such a message.
| Assignee | ||
Comment 1•2 years ago
|
||
Depends on D194645
Pushed by choller@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a021bb2b97e1
Handle special messages in IPC fuzzing. r=truber
Comment 3•2 years ago
|
||
Backed out for causing build bustage at tools/fuzzing/ipc/IPCFuzzController.cpp
Backout link: https://hg.mozilla.org/integration/autoland/rev/51a3947c7373d9ef2b849d795e31efd766f90dee
Flags: needinfo?(choller)
Pushed by choller@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b8d59b82d2d8
Handle special messages in IPC fuzzing. r=truber
Comment 5•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
| Assignee | ||
Updated•2 years ago
|
Flags: needinfo?(choller)
You need to log in
before you can comment on or make changes to this bug.
Description
•