Open Bug 1477242 Opened 7 years ago Updated 3 years ago

Stop running STS polling thread on child processes, use XPCOM thread instead

Categories

(Core :: Networking, enhancement, P3)

Product:
Core
Component:
Networking
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox63 --- affected

People

(Reporter: mayhemer, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Even though networking should be completely sandboxed (disabled) in content processes, we still run the full STS thread dependent on local socket pair polling to wake up. This is no longer necessary and we can just run a normal xpcom thread instead. This will just fix bug 1404409. Then we can also completely remove the parent->child priority messaging added in bug 1442178. Any objections?
webrtc was using it? They do not need it any more?
Webrtc treats content-process STS as just another thread, so this would be fine.
Whiteboard: [necko-triaged]
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.