558549 - [OOPP] Plugin container process name should include Mozilla product name

Status: RESOLVED WONTFIX

(Core :: IPC, defect)

Description

[Bill Gianopoulos [:WG9s]]

Bug 55819- changed the process name for the plugin process from mozilla-runtime to plugin-container.

This is a good change as it makes it easier for the average user to determine what it is for.  Unfortunately it did not go far enough.  There is still an issue for Operating systems such as Windows/XP, where it is difficult to determine the parent process.

The default task manager also does not display the "pretty name" referred to in that bug.

So, for the case where a user is running multiple Mozilla products that employ OOPP there is no way to tell which process belongs to which product.  I think the name should be of the form firefox-plugin, seamonkey-plugin, etc.

Comment 1

[(mostly gone) XtC4UaLL [:xtc4uall]]

(In reply to comment #0)
> Bug 55819- changed the process name for the plugin process from mozilla-runtime
> to plugin-container.

For reference: it was Bug 558190.

Comment 2

[Volker E.]

I didn't think too much about the new process after installing 3.6.4beta on Windows XP and when I started up Task manager and saw 'plugin-container.exe' some days after installation at the first look I thought it's some kind of trojan or unwanted service process, because of lacking connection to Mozilla Firefox.

Comment 3

[Bur]

Yes, that name is confusing. Plugin-container to me somehow sounds like an adware codec pack or plugin for video streaming. And since that process also takes quite some RAM I guess many people will wonder what it actually does.

Why not name it firefox-plugins.exe?

Comment 5

[Cameron McCormack (:heycam)]

Agreed.  Also, would it be feasible to set the name at runtime to include the plugin that it is hosting?  firefox-flash-plugin-container.exe or so.

Comment 6

[Andrew McCreight [:mccr8]]

I think there have been multiple back and forths about what the right name should be for content processes in the decade since this was filed, so let's just close this.