Closed Bug 1866465 Opened 2 years ago Closed 2 years ago

Handle special message types

Categories

(Core :: Fuzzing, enhancement)

x86_64
Linux
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:

  1. They need special synchronization, otherwise they will cause timeouts (as they will never generate a MessageTask even though the implementation expects one).

  2. 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.

Pushed by choller@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a021bb2b97e1 Handle special messages in IPC fuzzing. r=truber
Pushed by choller@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b8d59b82d2d8 Handle special messages in IPC fuzzing. r=truber
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
Flags: needinfo?(choller)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: