Implement NPN_ReloadPlugins for out-of-process Plugins

RESOLVED FIXED in Firefox 13



5 years ago
5 years ago


(Reporter: spohl, Assigned: Josh Aas)


Windows 7

Firefox Tracking Flags

(firefox13+ fixed, firefox14+ fixed, firefox15+ fixed)



(1 attachment, 1 obsolete attachment)

2.72 KB, patch
Benjamin Smedberg
: review+
Details | Diff | Splinter Review


5 years ago
User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)

Steps to reproduce:

As of version 11.2, Flash Player will attempt to update in the background even if it is loaded by Firefox. At runtime, Flash Player performs checks to see if the latest version is being used. If not, Flash Player will call NPN_ReloadPlugins(FALSE) to load the latest version for any future instances.

Actual results:

NPN_ReloadPlugins isn't implemented for out-of-process Plugins. See dom/plugins/ipc/PluginModuleChild.cpp:

_reloadplugins(NPBool aReloadPages)
    NS_WARNING("Not yet implemented!");

Expected results:

NPN_ReloadPlugins should be implemented for out-of-process Plugins.
Component: Untriaged → Plug-ins
Ever confirmed: true
Product: Firefox → Core
QA Contact: untriaged → plugins


5 years ago
Assignee: nobody → joshmoz

Comment 1

5 years ago
Created attachment 626984 [details] [diff] [review]
fix v1.0

This is entirely untested, ran out of time today. It might work, it might need a bit more work.

Comment 2

5 years ago
Note: We might want to consider making the IPC call async. I made it sync for the first try in case there were dependencies in js code expecting plugins to be properly reloaded after the call.

Comment 3

5 years ago
Created attachment 627020 [details] [diff] [review]
fix v1.1

This seems to work, just switched the IPC call to async in this revision of the patch. Can you verify that this works for you, Stephen?
Attachment #626984 - Attachment is obsolete: true
Attachment #627020 - Flags: review?(spohl)

Comment 4

5 years ago
(In reply to Josh Aas (Mozilla Corporation) from comment #3)
> Created attachment 627020 [details] [diff] [review]
> fix v1.1
> This seems to work, just switched the IPC call to async in this revision of
> the patch. Can you verify that this works for you, Stephen?

Your patch looks good to me. It correctly initiates the refresh of the plugins and ends up executing the same code path that about:plugins would.

I can't set the flag to "review+" on the attachment though.

Comment 5

5 years ago
(In reply to Stephen A Pohl from comment #4)

> I can't set the flag to "review+" on the attachment though.

Don't worry about it, your comment is enough. Thanks.


5 years ago
Attachment #627020 - Flags: review?(spohl) → review?(benjamin)


5 years ago
Attachment #627020 - Flags: review?(benjamin) → review+

Comment 6

5 years ago
try server run:

Comment 7

5 years ago
pushed to mozilla-inbound

Comment 8

5 years ago
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla15
Josh/Benjamin - how would we feel about uplifting this and bug 686335 across trains? I'm looking for ways to make it easier for Adobe to push out fixes. Are these 14-safe? Are they 13.0.2 safe?
tracking-firefox14: --- → ?

Comment 10

5 years ago
Comment on attachment 627020 [details] [diff] [review]
fix v1.1

Bug caused by (feature/regressing bug #): unimplemented NPAPI feature for OOPP
User impact if declined: Flash would not be able to trigger the browser to load a new version on upgrade
Testing completed (on m-c, etc.): unknown
Risk to taking this patch (and alternatives if risky): This seems fairly low-risk to me: the same basic codepath happens any time a user loads about:plugins or a page tries to load a new/unknown plugin.
String or UUID changes made by this patch: none

I'd probably also be comfortable taking this in a 13.0.2
Attachment #627020 - Flags: approval-mozilla-beta?
Comment on attachment 627020 [details] [diff] [review]
fix v1.1

[Triage Comment]
This may need to go into 13.0.2, so it should definitely land in our next beta.
Attachment #627020 - Flags: approval-mozilla-beta? → approval-mozilla-beta+


5 years ago
tracking-firefox13: --- → ?
tracking-firefox14: ? → +
Comment on attachment 627020 [details] [diff] [review]
fix v1.1

[Triage Comment]
Please land on mozilla-release asap so that we can test using a tinderbox build. This is not yet shipping in a 13 release, however.
Attachment #627020 - Flags: approval-mozilla-release+
Landed on beta/release at akeybl's behest:
Blocks: 767612
As with bug 686335...

FYI, QA will be going through the following testplan the next few hours with the latest Nightly:

Please email me at with any red flags or revisions you see necessary to giving you the results your need to make any final calls for 13.0.2.


5 years ago
status-firefox13: --- → fixed
status-firefox14: --- → fixed
status-firefox15: --- → affected
tracking-firefox13: ? → +
tracking-firefox15: --- → +


5 years ago
status-firefox15: affected → fixed
You need to log in before you can comment on or make changes to this bug.