Repository navigation
"fs.openSync" results in an abort #37804
Description
- 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: fs.openSync
What steps will reproduce the bug?
Setup a node instance,
» node
and run the following javascript code.
fs = require('fs'); fs.openSync("", 1000000000000000, null);
Then an abort occurs.
How often does it reproduce? Is there a required condition?
This abort 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.
> fs = require('fs'); fs.openSync("", 1000000000000000, null)
node[57303]: ../src/node_file.cc:1712:void node::fs::Open(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[1]->IsInt32()' failed.
1: 0xa03530 node::Abort() [node]
2: 0xa035ae [node]
3: 0xa099c2 [node]
4: 0xbe369b [node]
5: 0xbe4c46 [node]
6: 0xbe52c6 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node]
7: 0x13ff259 [node]
[1] 57303 abort (core dumped) node
Activity
aduh95 commentedon Mar 19, 2021
Duplicate of #37430.
Fixed by #37480, fix will be released with Node.js v16.0.0.