perf_hooks.monitorEventLoopDelay results in an abort

[zyscoder]

• Version: v14.15.1
• Platform: Linux 5.8.0-38-generic The binary and long term compatibility with node #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
• Subsystem: perf_hooks.monitorEventLoopDelay

What steps will reproduce the bug?

Setup a node instance,

» node

and run the following javascript code.

perf_hooks.monitorEventLoopDelay({resolution:2147483648})

Then an abort occurs.

How often does it reproduce? Is there a required condition?

This problem can always be triggered following the steps above.

What is the expected behavior?

If any error occurs, an exception or other similar error-reporting stuff should be thrown. There is no reason to abort the whole node process.

What do you see instead?

» node
Welcome to Node.js v14.15.1.
Type ".help" for more information.
> perf_hooks.monitorEventLoopDelay({resolution:2147483648})
node[802902]: ../src/node_perf.cc:483:void node::performance::{anonymous}::ELDHistogramNew(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `(resolution) > (0)' failed.
 1: 0xa03530 node::Abort() [node]
 2: 0xa035ae  [node]
 3: 0xa6d5ea  [node]
 4: 0xbe4695  [node]
 5: 0xbe4c9f  [node]
 6: 0xbe52c6 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node]
 7: 0x13ff259  [node]
[2]    802902 abort      node

Additional information

[aduh95]

Can reproduce on master.