Ok, speaking to delphick@ about this, he had a similar issue when setTimeout slightly changed how tasks were scheduled, and console messages failing to infer their source location. This sounds plausible for changes in the yielding behaviour of parser blocking scripts.
Unfortunately, I can't simply rebaseline the tests, because the behaviour is different between Debug and Release (seemingly because of timing differences).
I might end up suppressing these deprecation messages, but that's not a great long-term fix...
Comment 1 by bugdroid1@chromium.org
, Oct 12