Heap out of memory
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0xb2c2b0 node::Abort() [PM2 v5.1.2: God Daemon (/root/.pm2)]
2: 0xa4025c node::FatalError(char const*, char const*) [PM2 v5.1.2: God Daemon (/root/.pm2)]
3: 0xd1d11e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [PM2 v5.1.2: God Daemon (/root/.pm2)]
4: 0xd1d497 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [PM2 v5.1.2: God Daemon (/root/.pm2)]
5: 0xed68f5 [PM2 v5.1.2: God Daemon (/root/.pm2)]
6: 0xed73d6 [PM2 v5.1.2: God Daemon (/root/.pm2)]
7: 0xee704c [PM2 v5.1.2: God Daemon (/root/.pm2)]
Contributor guide
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
Start with the reported PM2 v5.1.2 daemon stack trace and reproduce the JavaScript heap exhaustion under the same environment. The issue does not identify a file, entry point, workload, or reproduction steps, so first determine what operation causes the daemon to exceed the heap; done means the cause is understood and the daemon no longer reaches this failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100