Bug 142147 – A plug-in sometimes leaves MBP discrete GPU processor enabled after closing a window

• Status: RESOLVED
• Resolution: WONTFIX
• Component: New Bugs

[Jim Oase]

When a site is accessed that uses the MacBook Pro discrete GPU exiting that site does not release the discrete GPU.  Leaving the GPU causes excessive battery drain and heat build up.

This site requires a password but is an example... http://www.video.theblaze.com/video/v37708683/0225-cain-conversation

[Jim Oase]

Created attachment 247632 [details]
Reason the discrete GPU can not be turned off after leaving site that used it.

[Alexey Proskuryakov]

This dialog claims that it's due to a plugin.

[Tim Horton]

Don't we keep the plugin process up for a while after last using the plugin? Does it resolve itself after a minute or something?

[Jim Oase]

There have been occasions when the discrete GPU is deactivated after closing a site that activates the discrete graphic processor.  

So far the process to accomplish deactivation of the GPU is not repeatable.  Time is a function but the period is variable.  Sometimes over night does not affect the deactivation other times 10 minutes is sufficient.

Causing discrete GPU activation and deactivation by launching and closing iPhoto is consistently immediate.

[Alexey Proskuryakov]

If the same plug-in type (e.g. Flash) is in use in any other browser window, that would keep the process alive. 

I think that this should be primarily a bug report against the plugin vendor.

[Jim Oase]

(In reply to comment #5)
> If the same plug-in type (e.g. Flash) is in use in any other browser window,
> that would keep the process alive. 
> 
> I think that this should be primarily a bug report against the plugin vendor.

Thanks I will check that out... my only plug in is Flash.

[Jim Oase]

(In reply to comment #6)
> (In reply to comment #5)
> > If the same plug-in type (e.g. Flash) is in use in any other browser window,
> > that would keep the process alive. 
> > 
> > I think that this should be primarily a bug report against the plugin vendor.
> 
> Thanks I will check that out... my only plug in is Flash.

Just occurred to me... doesn't have that problem with Safari which also uses Flash.  What is different?

[Jim Oase]

Created attachment 247955 [details]
Indicates the plugin being left active after the site using it is inactive.

[Jim Oase]

(In reply to comment #5)
> If the same plug-in type (e.g. Flash) is in use in any other browser window,
> that would keep the process alive. 
> 
> I think that this should be primarily a bug report against the plugin vendor.



There is a plug in  com.apple.WebKit.Plugin.64.Deveolopment   being left on after the site using the discrete processor is closed.


Safari doesn't use the plugin and doesn't have the problem.

[Jim Oase]

(In reply to comment #6)
> (In reply to comment #5)
> > If the same plug-in type (e.g. Flash) is in use in any other browser window,
> > that would keep the process alive. 
> > 
> > I think that this should be primarily a bug report against the plugin vendor.
> 
> Thanks I will check that out... my only plug in is Flash.


When returning from sleep the discrete processor is being turned on.  This is after operating with the same windows for a half hour.  None of those windows caused the discrete processor to be activated.

After a minute or two the discrete processor is turned off again.

I will attach a screen shot from the Activity Monitor showing that the Flash Player (SafariForWebKitDevolopment Internet Plug-in) in is being activated and then inactivated.

[Jim Oase]

Created attachment 248198 [details]
Screen shot showing Flash plug-in being activated after waking from sleep.

[Anders Carlsson]

I don't really know if there's anything actionable here. We keep the flash plug-in running for a while even if there are active plug-ins, just to make instantiating the next plug-in faster.

[Jim Oase]

(In reply to comment #12)
> I don't really know if there's anything actionable here. We keep the flash
> plug-in running for a while even if there are active plug-ins, just to make
> instantiating the next plug-in faster.

Good idea if all the computers have wall plugs, questionable idea for those with portables, like my MacBook Pro, and concerns about battery life.

The recent epidemic of MacBook Pro GPU failures highlights the problem with keeping the plug-in active.  Machines with suspect discrete GPUs can run on the integrated GPU. Therefore they can run Safari but not WebKit if they avoid site that use Flash.

The Flash plug-in will activate and stay on after reviving from sleep even when no Flash site has been visited.

[Ahmad Saleem]

NPAPI and Webkit Plugins are not supported any more. Can this be marked as "RESOLVED WONTFIX"? Thanks!