UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36

Steps to reproduce the problem:
1. go to Chrome Settings > Content Settings and enable "Block sites from running Flash"
2. browse around on the web and watch the Task Manager
3. note the appearance of "Plugin Broker: Shockwave Flash" and how it's using approximately 10K memory

What is the expected behavior?
When chrome://plugins existed, users could fully disable Flash Player. Since the removal of chrome://plugins, we've been told that disabling "Block sites from running Flash" in Content Settings accomplishes the same thing as disabling the plugin. So why is chrome still giving memory to something that I want COMPLETELY disabled/removed?

What went wrong?
chrome://plugins should never have been removed until another fully functional method of completely disabling Flash Player (and other plugins) was realized.

Did this work before? Yes < Chrome 55/56

Chrome version: 57.0.2987.98  Channel: stable
OS Version: 
Flash Version: 

How do I completely stop Flash Player from getting access to any resources? How do I completely disable it?