Closed
Bug 1090573
Opened 10 years ago
Closed 9 years ago
Disable Windows deferred message protection for the PPlugin protocol
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(e10s+)
RESOLVED
DUPLICATE
of bug 1160140
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: billm, Unassigned)
References
Details
This is a follow-up for bug 641685. It seems like we probably don't need Windows deferred message protection for channels connecting the plugin process to a content process. We should experiment with turning this off.
Reporter | ||
Updated•10 years ago
|
Component: IPC → Plug-ins
Comment 1•10 years ago
|
||
The Holy Grail of plugin bugs!
Updated•10 years ago
|
tracking-e10s:
--- → +
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Depends on: 1093693
Resolution: --- → WONTFIX
Summary: Figure out if Windows deferred message protection is needed for plugins with e10s → Disable Windows deferred message protection for the PPlugin protocol
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Updated•9 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 9 years ago
Resolution: --- → DUPLICATE
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•