NodeJS crash
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 326
- PR merge metrics
- No merged PRs in 30d
Description
1: 0xa3ac30 node::Abort() [/home/user/.nvm/versions/node/v14.5.0/bin/node] 2: 0xaae1d9 [/home/user/.nvm/versions/node/v14.5.0/bin/node] 3: 0xc19bab [/home/user/.nvm/versions/node/v14.5.0/bin/node] 4: 0xc1b156 [/home/user/.nvm/versions/node/v14.5.0/bin/node] 5: 0xc1b7d6 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [/home/user/.nvm/versions/node/v14.5.0/bin/node] 6: 0x13f5159 [/home/user/.nvm/versions/node/v14.5.0/bin/node]
I have this meaningless crash when I try to run a simple NestJS-based app - after manually patching bug with cli-color.
There is nothing interesting in the core dump as well, and it doesn't seem to be related to native modules.
Node version: 14.12.0/14.5.0 - same bug
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is named. Start by reproducing the simple NestJS-based app after the cli-color patch under Node 14.5.0 and 14.12.0, then compare the crash behavior and available core-dump information; done means the cause is identified and the crash no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100