iron-node is doing something weird with native functions

[jamestalmage]

Reproduction here:

git clone git@github.com:jamestalmage/__iron-node-issue.git
cd __iron-node-issue
npm install
npm test

Reference: avajs/ava#475 (diff)

[s-a]

@jamestalmage thanks for the detailed repro repo. You are doing heavy professional stuff with that thing 😄

On my system ironNode (2.1.13) alerts

which I guess depends on chrome and sounds to make sense. It could be a result of calling native methods in different context. So I tried...

.setTimeout.bind(window) and module.exports.setTimeout = setTimeout.bind(window);

Please check out the Pull Request. Both of them make your profiling work 👍
If you can confirm that behaviour Id like to change the title to "iron-node is doing something weird with native functions"

[jamestalmage]

I don't think it's iron-node, apparently it's just Chrome being weird. (even when iron-node is not involved)

[s-a]

https://bugs.chromium.org/p/v8/issues/detail?id=4718