Tested about one hour ago with both Canary and the latest stable Chrome build (with web audio enabled). If no microphone/headset is connected to the computer, the browser will eat 100% of the CPU before the user allows or denies microphone access, causing the system to be inoperable. Of six tests on Windows 7, this happened every time, resulting in a forced restart once, and failure to execute ctrl-alt-del once. The other four times, I was able to force quit the browser.
Tested about one hour ago with both Canary and the latest stable Chrome build (with web audio enabled). If no microphone/headset is connected to the computer, the browser will eat 100% of the CPU before the user allows or denies microphone access, causing the system to be inoperable. Of six tests on Windows 7, this happened every time, resulting in a forced restart once, and failure to execute ctrl-alt-del once. The other four times, I was able to force quit the browser.