Chrome Version: (58.0.2997.0 (Official Build) unknown (64-bit)
OS: (ChromeOS (testing image))

What steps will reproduce the problem?
(1) Ensure SSH is enabled on the ChromeOS device.
(2) Run any Chrome kiosk application on the ChromeOS device.
(3) Press Ctrl-Alt-F2 on the ChromeOS device to access the developer shell.
(4) In the developer shell, run 'top' and then press '1' to see per core CPU usage. 
(5) Run 'ssh -L 9222:localhost:9222 root@YOUR_HOST -N' on your desktop, not the ChromeOS machine, to create an SSH tunnel for debugging.
(6) Go to localhost:9222 on your desktop machine and open a debugging session for the kiosk application page.
(7) invoke the chrome.feedbackPrivate.getSystemInformation with any callback. In this case I used console.log but it doesn't really matter.
(8) wait for callback to be invoked, watching the top session on the ChromeOS device.

What is the expected result?

The callback is invoked in a short amount of time (<2 seconds would be nice, but I'm not the ultimate judge here) and does not increase CPU usage significantly.

What happens instead?

The callback is invoked at roughly 10 seconds after calling the API. Roughly 5 seconds after calling the API one of the CPU cores spikes to 100% usage and stays there for several seconds, caused by one of the chrome processes.

Please let me know if you need more information. I've never filed a Chrome bug before so I may have left out something important.