It is still a bit forward looking, but I can give you one quick "for instance":

Using the data that is being collected today, we can analyze poor performance and stability and correlate it with certain extensions and plugins, going down to the level of version and platform specifics. We can then provide better blocklisting based on this data, in addition to providing the user with the tool to see the results for themselves and offer suggestions such as updating an add-on or uninstalling it.

One way, which is admittedly heavy-handed, is already available. If you go to Help->Troubleshooting Information, there's a button to "Reset Firefox". https://support.mozilla.org/en-US/kb/reset-firefox-easily-fi... Hopefully future releases will automatically detect problems in individual subsystems and give you more fine-grained control.

Curious to see this today, as the FF enterprise mailing list has been filled with grumbling this week about FF's inability to auto-update itself or its plugins, and the headaches that causes us IT folk when paired with the auto-quarantining of outdated plugins recently implemented.