The design we want is probably something like this: 1. If a content process or a plugin process wants to reload plugins, it asks the chrome process to do so. 2. If the chrome process reloads plugins and finds new ones, it broadcasts them to all content processes.

Benjamin, can you explain why you think this is a dupe of bug 1096203?

Plugins bundled as part of addons are registered "late", after Firefox has started up. I concluded that we had already created the content process by that point and therefore the new plugin registration wasn't being sent over properly, which would be fixed by this bug.

Hi Benjamin, I tried the latest Nightly (39.0a1 2015-03-24), it seems that both the bug 1096203 and bug 1081991 are fixed. Does it mean this bug has been fixed already by some other bug(s) fixing?

I don't know. Please ask the people who fixed those bugs.

(In reply to Pin Zhang [:pzhang] from comment #4) > Hi Benjamin, I tried the latest Nightly (39.0a1 2015-03-24), it seems that > both the bug 1096203 and bug 1081991 are fixed. Does it mean this bug has > been fixed already by some other bug(s) fixing? Hi Bill, should we close this bug?

I don't think we should close this. There's still work to be done afaik. It sounds like your bugs were not related to this bug. I suspect bug 1083281 might have fixed your problem.

Thanks.

billm, is this still relevant?

I think so.

Bill and Benjamin, should we close this? or do something with it?

This is still behind several user-visible regressions such as bug 1247042.

ddurst, this should perhaps be on our plugin-work radar. It's not part of the test pilot project, but it's an e10s regression that could be a problem if there's a 0-day Flash update.

Indeed. Going to block 1282484 because I can't imagine it won't come up. (We probably need a wider meta bug for all this related work.)

Related: test_refresh_navigator_plugins doesn't work with e10s because of this same underlying issue.

Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information

Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information

Resolving as wont fix, plugin support deprecated in Firefox 85.