Chrome crashing with adobe flashplayer plugin

Question

Operating system Windows 10 EnterpriseWeb browser Google Chrome version 53.0.2785.116 m (64-bit)Adobe Flashplayer version 23.0.0.166Open any page with flash content and Google Chrome crashexample: https://helpx.adobe.com/es/flash-player.htmlIf you get error messages, please quote them exactly, or provide a screenshot[Window Title]Google Chrome[Main Instruction]Google Chrome has stopped working[Content]A problem caused the program to stop working correctly. Please close the program.[Close the program]If I disable flashplayer plugin the errors goes away.

wakko2005 · Accepted Answer

Just for grins, lets try disabling hardware acceleration.

Instructions are in the video troubleshooting guide, below:

https://helpx.adobe.com/flash-player/kb/video-playback-issues.html

If you're still stuck, please follow the directions in the guide on providing the dxdiag report and additional information about what you tested and saw.

If you can, it would be *really* helpful if you can grab the crash dump from Chrome:

Report a Flash Player crash or error

I have been able to fix the issue. As you mention it looks there was a corrupted file on my laptop.

What I did was to delete all content on following directory

C:\Users\<YourID>\AppData\Local\Google\Chrome\User Data\PepperFlash

I test my browser and it was working fine. Then I go to chrome://components/

and click on search updaes for pepper_flash - Versión: 23.0.0.166

It download plugin again and it keeps working fine.

jeromiec83223024 · Answer

First things first, if you haven't rebooted since you started experiencing this issue, start there.

If the problem persists, there's a good chance the Flash Player included with Chrome was corrupted somehow. The easiest approach is to just remove and reinstall Chrome.

Based on the symptoms, I'm leaning towards a client-side problem -- either a corrupted binary, or maybe a weird permission thing, like a group policy that's applied in your enterprise, which restricts access to required files or registry keys that we would assume normal access to.

Google has excellent telemetry, and is very fast to raise new issues like this in the field. This is definitely not a widespread issue on the radar at the moment.

It's also possible that it's a driver thing. Early Conextant audio drivers on Win10 were very problematic, but aside from that, driver-related stability issue would typically be limited to video or 3D content.

If you're still stuck, let us know, and we can collect more detailed forensics.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded