The Processes tab in the Fall Creators Update (October 2017) version of the Windows task manager will group processes by path (putting all chrome.exe processes together, which is great) and can display per-process names. Edge uses this to display tab names and other process names (Background Tab Pool, Chakra JIT Compiler, etc.). Chrome should do this as well.

Many users know about the Windows Task Manager but do not know about Chrome's Task Manager. Labeling our processes would make it much easier for these users to identify which tab is causing problems. Better attributability is important.

The Windows Task Manager is also (now) better at summarizing total Chrome CPU and memory usage, so we should leverage that.

Screenshot here:
https://twitter.com/JenMsft/status/923996264580071425

I don't know what the task naming API is but I assume that we can track it down easily enough. This should be a relatively straightforward way to expose Chrome performance information to a *lot* more people.