Chrome's Pepper Flash Will NOT Remain Disabled Anymore
Reported by ckats...@gmail.com, Feb 6 2013
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17 Steps to reproduce the problem: 1. Have more than one version of Flash installed on the computer. 2. In Chrome settings, disable Pepper Flash and enable a plug-in version. 3. Close Chrome and re-open it. Check Plug-in settings again, and find that Pepper Flash has re-enabled itself, causing two versions of Flash to be enabled at the same time. *Also, Pepper Flash will re-enable even during the same browsing session (not closing the browser, just opening new pages) What is the expected behavior? When disabled, and when it's not the only installed version of Flash on the computer, Chrome's Pepper Flash should remain disabled until and unless the user chooses to enable it again. What went wrong? Apparently in the last Chrome update, something was changed that forces the Pepper Flash version to continuously re-enable itself (become active) -- even when another version of Flash is enabled by the user -- causing two versions active at the same time. This results in constant page loading problems, sluggish performance, and crashes. Did this work before? Yes Prior to the most recent update of the Chrome browser (version 24) Chrome version: 24.0.1312.57 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) The only work-around solution to prevent Pepper Flash from constantly re-enabling itself is to leave the Plug-ins settings page open in a separate tab, for the entire browsing session, every browsing session. The only alternative choice is to use Chrome's Pepper Flash and keep other plug-in versions disabled instead.
Feb 6 2013,
The fix should be in the works- see issue 150596 . If you're in a hurry, grab the latest Chrome Canary version. The performance issues, distortions, snow, crashing, etc. in PPAPI Flash are unfortunately still not fixed yet, but they're working on them. You can help. Post the contents of your chrome://gpu , chrome://flash , and/or chrome://tracing screens to the appropriate issue (ex: Issue 140637 or Issue 161307 ).
Feb 6 2013,
Okay, I see now that the issue has been a problem for awhile. In the past, it did happen to me occasionally, but was random... and though annoying to fix, when I disabled Pepper Flash again, it would stay disabled. For me, the problem with Pepper Flash constantly re-enabling itself started with the last Chrome update. Not only does it re-enable itself upon restarting the browser, but it also re-enables itself during my ongoing browser session. When I launch a game using Flash, it triggers Pepper Flash to re-enable again, even though I disabled it when I first opened my Chrome browser. As I mentioned above, the only way I can keep it disabled is by leaving the Plug-ins page opened in a separate tab the entire time I'm using Chrome.
Feb 6 2013,
Version 24.0.1312.57 m OS Windows 7 & XP (SP3) I also have this problem on both XP and Windows 7, this was working last week. This problem has described and been fixed in previous version of chrome ( Issue 150596 : Pepper Flash is re-enabled automatically after the user manually disables it).
Feb 11 2013,
Please suggest the solution to permanently disable pepper flash
Feb 11 2013,
I am also having this problem in Vista
Feb 15 2013,
I am having the same issue and it is highly annoying. Is there any permanent way I can disable pepper flash as it definitely interferes with my game play. It causes the game to slow down and then flash crashes..
Feb 20 2013,
the same problem... google what are you doing?
Feb 20 2013,
Same problem here. That is so annoying that I'm considering going back to the Opera now ;/
Feb 23 2013,
Can we get somebody to close as dupe of issue 150596 ? This bug has already been fixed, as comment #1 points out. If you can't wait for the next update that includes the fix, then either get the Canary dev version or switch. This bug irritates me too but I'm willing to wait. In the meantime I have an about:plugins tab pinned and I already use the "open my tabs from last time" feature, so I can disable it quickly when I load Chrome.
Feb 23 2013,
To nmessen... This bug has NOT already been fixed. It won't be fixed until Pepper Flash stops re-enabling itself in CHROME. There's been no official feedback, and no official response telling us when that Chrome update will finally show up. I'm really tired of reading replies that tell me to "get Canary" if I'm in a hurry. If I wanted to use the Canary browser, I'd use it. I use Chrome. I have all of my bookmarks in Chrome. If Canary is so great, then maybe it should be the "Stable" version, and Chrome should go back into Beta! As for this being a duplicate and you wanting it closed... Seriously??? This topic has remained "unconfirmed" and completely ignored by Google staff. They could care less about my "duplicate" issue, or any of the many other "duplicate" conversations that currently exist about this problem. But it gives frustrated Chrome users a convenient place to express their complaints, to know that they're not alone. If that irritates you, then perhaps you should go to the Canary forums or groups instead -- or stop reading this discussion. ;)
Feb 25 2013,
Those of you on Windows trying to keep Pepper Flash disabled, Pepper can be disabled at Chrome startup. Not sure if this works around the issue described in this ticket, but it's worth a shot. Try setting up a desktop shortcut with the following flag on the Target field of the shortcut: --disable-bundled-ppapi-flash Example: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-bundled-ppapi-flash
Feb 26 2013,
They finally fixed the problem, with the recent Chrome update. They created NEW problems with that update... but that's for another discussion. Pepper Flash will now stay disabled when we disable it.
Jul 29 2013,
closing this issue as per comment #13, please raise new one if you are seeing this in future or any similar problem.
Mar 25 2014,
This is not fixed. We still can't permanently disable PepperFlash, it is automatically re-enabled at each Chrome restart. The only solution that works is by deleting the PepperFlash dll files: https://productforums.google.com/d/msg/chrome/ufkQg9N-L0s/M8PnEu4QCQ4J PepperFlash causes audio issues (https://code.google.com/p/chromium/issues/detail?id=350551) and display drivers crashes on my computer (https://code.google.com/p/chromium/issues/detail?id=350547), this is the most horrible thing I have ever come across, you should seriously consider to disable it by default.
Sign in to add a comment