-
-
Notifications
You must be signed in to change notification settings - Fork 33.1k
Closed
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.fsIssues and PRs related to the fs subsystem / file system.Issues and PRs related to the fs subsystem / file system.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.
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.chownSync
What steps will reproduce the bug?
Setup a node instance,
» node
and run the following javascript code.
fs.chownSync("",-1, -1)
Then the node instance crashes.
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.chownSync("",-1, -1)
node[51145]: ../src/node_file.cc:2179:void node::fs::Chown(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[1]->IsUint32()' failed.
1: 0xa03530 node::Abort() [node]
2: 0xa035ae [node]
3: 0xa0d54a [node]
4: 0xbe369b [node]
5: 0xbe4c46 [node]
6: 0xbe52c6 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node]
7: 0x13ff259 [node]
Additional information
ycjcl868
Metadata
Metadata
Assignees
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.fsIssues and PRs related to the fs subsystem / file system.Issues and PRs related to the fs subsystem / file system.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.