Chrome Version: 58.0.3007.0 (Official Build) dev (64-bit)
OS: ChromeOS

What steps will reproduce the problem?
(1) Sign-in to ChromeOS.
(2) Immediate navigate to a site that uses Text-To-Speech, e.g. https://www.guardian.co.uk/
(3) Open Task Manager.

What is the expected result?

Expect to see processes listed for the signed-in user.

What happens instead?

Several processes are listed for profile "First User":
A. Incognito Extension: Lock Screen
B. Extension: Chrome OS built-in text-to-speech extension

(B) loads because of step #2 (even though the tab which actually called the TTS API was in a different profile; see  issue 616636 ).

What's strange is that (A) stays loaded as well, whereas if you skip step #2 then you'll find that any lingering "First User" processes soon exit.

Not sure if this is a regression or not, but I've only noticed it in M58.