Closed Bug 1178258 Opened 9 years ago Closed 9 years ago

[e10s] Implement a event loop heartbeat for the browser and plugin processes

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86
Windows
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(e10s+, firefox42 affected)

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
e10s + ---
firefox42 --- affected

People

(Reporter: jimm, Unassigned)

References

Details

What I'd like to do is add a low priority native event heart beat for both the plugin and browser process. This would be a safety net around our event processing designed to break us out of stacks like the one in bug 1178257. When we receive the event we check the queue for messages that should have been delivered but weren't for some reason and deliver them. The event I'm thinking we should use is a WM_TIMER, which a low priority event generated by the system.
This sounds like it will cause a lot of wakeups. In general we shouldn't have this while the user isn't active, to save power.
I don't think this is needed anymore.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.