Closed Bug 874016 (e10s-plugins) Opened 11 years ago Closed 3 years ago

[meta] [e10s] Plugin issues tracking

Categories

(Core Graveyard :: Plug-ins, defect)

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

Tracking

(e10s+)

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

People

(Reporter: playwatch, Unassigned)

References

Details

(Keywords: meta)

Attachments

(1 file)

Immagine.png
65.48 KB, image/png
Details
Attached image Immagine.png — 
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20130514 Firefox/24.0 (Nightly/Aurora)
Build ID: 20130514031031

Steps to reproduce:

I was trying the larch builds when I noticed this:

1-Start Firefox
2-Open more than one youtube tab


Actual results:

Firefox generates 1 plugin-container.exe process for each tab that uses flash (beyond the actual process for the tab) 


Expected results:

Firefox should create 1 process for each plugin, in order to avoid heavy resources usage.
Blocks: fxe10s
Component: Untriaged → General
Product: Firefox → Core
See Also: → 452272
Would it make sense to create a maximum of 2 processes per plugin (one for private mode, one for normal mode)?
This had nothing to do with that old e10s metabug (?).
Component: General → Plug-ins
Note: this would be a pretty significant chunk of work to implement, although it has the potential to significantly improve our hang and jank profile. It will require working through a bunch of questions about nested event loops triggered by plugins.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
Summary: Firefox shouldn't create more than one process for each plugin → When running content processes, Firefox shouldn't share a plugin process for all content processes
No longer blocks: fxe10s
This should be *should* share a process, right now we have no machinery to do that and plugins don't work in e10s properly.
Assignee: nobody → jschoenick
Status: NEW → ASSIGNED
OS: Windows 7 → All
Hardware: x86_64 → All
Summary: When running content processes, Firefox shouldn't share a plugin process for all content processes → [e10s] Firefox should share a plugin process for all content processes
Alias: plugins-e10s
Priority: P3 → P2
Depends on: 923745
Depends on: 923746
Depends on: 927224
Depends on: 961361
No longer depends on: 961361
Depends on: 992607
I'm going to split out the "share a plugin process" part into its own bug, since there are other major issues (windowed plugins) and this is already being used as a metabug.
Summary: [e10s] Firefox should share a plugin process for all content processes → [e10s] Plugin issues tracking
Depends on: 997483
Depends on: 921916
Depends on: 961361
Depends on: 987050
Whiteboard: [m1 blockers]
Whiteboard: [m1 blockers] → [m1 blockers][33 merge date: 2014-07-21]
Whiteboard: [m1 blockers][33 merge date: 2014-07-21] → [m1 blockers]
Blocks: 942707
Depends on: e10s-plugin-ipc
Blocks: old-e10s-m2
No longer blocks: e10s-m1
No longer blocks: 942707
Depends on: 1036135
No longer blocks: old-e10s-m2
No longer depends on: jsplugins-base
Depends on: 1041611
No longer depends on: 1041611
Depends on: 1056343
Depends on: 1056385
Depends on: 1044182
Alias: plugins-e10s → e10s-plugins
Depends on: 1071378
Depends on: 1078087
Depends on: 1081204
Depends on: 1081991
Depends on: 1080916
Depends on: 1072342
Depends on: 874167
Depends on: 963358
Depends on: 1088840
No longer depends on: jsplugins-streams
No longer depends on: jsplugins-params
Depends on: jsplugins
Depends on: 1092121
Depends on: 1095991
Depends on: 1096203
Assignee: john → jmathies
Depends on: 1092630
Depends on: 1099863
Depends on: 1093693, 1098055, 1096664, 1096080
Depends on: 1098057
No longer depends on: jsplugins
Depends on: 1103177
Depends on: 1110887
Depends on: 1110884
No longer depends on: 1110884
Depends on: 1110888, 1113559
No longer depends on: 1088840
No longer depends on: 1080916
Depends on: 1127595
Depends on: 1127794
Depends on: 1128079
Depends on: 1128238
Depends on: 1130165
Whiteboard: [m1 blockers]
Depends on: 1130976
Depends on: 1137944
No longer depends on: 1127595
Depends on: 1138181
Depends on: 1140683
No longer depends on: 1140683
Depends on: 1148827
Depends on: 1148978
Depends on: 1150043
No longer depends on: 1148827
Depends on: 1155974
Depends on: e10s-hangs
No longer depends on: 1149253
Depends on: 1158788
Depends on: 1167978
Depends on: 1167532
No longer depends on: 1167978
Depends on: 1179245
No longer depends on: 1148978
Depends on: 1194661
Depends on: 1197581
Depends on: 1163570
Depends on: 1190364
No longer depends on: 1194661
Depends on: 1148978
Depends on: 1214878
No longer depends on: 1100252
Depends on: 1212813
Depends on: 1152049
Depends on: 1229455
Depends on: 1229164
Depends on: 1229429
No longer depends on: 1229164
Depends on: 1193055
Depends on: 1232184
Depends on: 1232302
Depends on: 1242273
Depends on: 1243413
Depends on: 1236210
Depends on: 1245972
Depends on: 1245994
Depends on: 1245995
Depends on: 1252233
Depends on: 1252877
Depends on: 1237853
Depends on: 1253748
Depends on: 1252874
Priority: P2 → --
Depends on: 1258058
Depends on: 1271898
Depends on: 1259780
Depends on: 1330003
Assignee: jmathies → nobody
Status: ASSIGNED → NEW
Summary: [e10s] Plugin issues tracking → [meta] [e10s] Plugin issues tracking
Resolving as wont fix, plugin support deprecated in Firefox 85.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: