Handle the case when we cannot get a dispatcher from LoadInfo in HttpChannelChild

NEW
Assigned to

Status

()

Core
Networking: HTTP
P3
normal
a year ago
7 months ago

People

(Reporter: kershaw, Assigned: kershaw)

Tracking

(Blocks: 1 bug)

Trunk
Points:
---

Firefox Tracking Flags

(firefox55 affected)

Details

(Whiteboard: [necko-backlog][QDL][BACKLOG][NECKO] )

(Assignee)

Description

a year ago
Please see bug 1343745 comment#14

In some cases, it's difficult to get a dispatcher from the channel's load info and SystemGroup is also not helpful here.

We have to figure out how to label the IPC actor and runnables under this circumstance.
(Assignee)

Updated

a year ago
Whiteboard: [necko-active]
(Assignee)

Updated

a year ago
Blocks: 1339676
(Assignee)

Updated

a year ago
Whiteboard: [necko-active] → [necko-active][QDL][TDC-MVP][NECKO]

Updated

a year ago
Priority: -- → P2
Whiteboard: [necko-active][QDL][TDC-MVP][NECKO] → [necko-active][QDL][BACKLOG][NECKO]

Updated

11 months ago
Priority: P2 → P3
(Assignee)

Updated

10 months ago
Whiteboard: [necko-active][QDL][BACKLOG][NECKO] → [necko-backlog][QDL][BACKLOG][NECKO]
You need to log in before you can comment on or make changes to this bug.