Closed Bug 1176296 Opened 10 years ago Closed 10 years ago

nsFrameMessageManager seems to have a phantom child that never receives JS messages

Categories

(Core :: DOM: Content Processes, defect)

Product:
Core
Component:
DOM: Content Processes
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: Yoric, Unassigned)

Details

While working on bug 1175098, I encountered a situation in which I broadcast to all children of the Global Process Message Manager, but only `childCount - 1` children receive the message. I don't know what's causing it, and it's a bit scary. Could this be the plug-in container?
Ok, that's embarrassing. This was most likely due to to a process that was too busy to respond within 1 second because it was loading a page. I will need to devise counter-measures around that.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.