Open Bug 1560638 Opened 5 years ago Updated 2 years ago

IPC messages from content process to socket process happen on main

Categories

(Core :: DOM: Networking, enhancement, P3)

Product:
Core
Component:
DOM: Networking
Type:
enhancement

Tracking

()

People

(Reporter: bwc, Unassigned)

Details

(Whiteboard: [necko-triaged])

Right now, when an IPC message is received on the content process, it is first dispatched to main. Given that we don't use main at all on the socket process, this imposes an extra hop, and a fairly significant efficiency penalty. It would be better if we could skip this, and either dispatch directly to STS, or perhaps call these callbacks on the IPC IO thread directly.

Bugbug thinks this bug is a enhancement, but please change it back in case of error.

Type: defect → enhancement

FWIW, we have similar setting in bug 1510691 (landed in larch) which is from Socket process to Content process in pBackground.

Priority: -- → P3
Whiteboard: [necko-triaged]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.