UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.2999.0 Safari/537.36

Steps to reproduce the problem:
1. Attach an expensive function to an event handler
2. Dispatch that event
3. View the Developer Console for an error starting with "[Violation]"

What is the expected behavior?
Scripts continue to work despite an apparent lag.

What went wrong?
The error "[Violation] 'readystatechange' handler took 213ms" was logged to the console and the rest of the script stopped executing.

Did this work before? N/A 

Chrome version: 58.0.2999.0  Channel: canary
OS Version: OS X 10.10.5
Flash Version: 

I'm sorry for the vague description. I am, for the first time, seeing messages in the console that only occur when viewing "Verbose" level logs that start with "[Violation]"
Another one I saw on the same page when I used my web application in such a way as to make the code work even harder is
"[Violation] 'requestAnimationFrame' handler took 148ms"

My concern is only if this behavior is intended to make it into the mainline code. I can understand functionality catching infinite loops or detecting deadlocks or something but a handler that takes less than 1/5 of a second kill the scripts on the page seems a little drastic.

I would also like to know if there is a way to turn off this feature in Canary as it is impeding functional tests (not that an unstable version of the application should be used for final functional tests anyway).

I just can't find any details on this new kind of error online anywhere.

Thanks.