Skip to content

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory #342

@jadmadi

Description

@jadmadi

Expected Behavior

Simply not to crash.

Actual Behavior

The application crashed unexpectedly during execution with a JavaScript heap out-of-memory error. Based on the logs, the process reached approximately 4090 MB before the Garbage Collector failed to reclaim sufficient memory, leading to a fatal crash.

`
<--- Last few GCs --->

[301212:0x1bcfa000] 856886 ms: Mark-Compact 4090.4 (4101.5) -> 4088.4 (4101.5) MB, pooled: 7.8 MB, 61.76 / 0.13 ms (average mu = 0.148, current mu = 0.030) allocation failure; scavenge might not succeed
[301212:0x1bcfa000] 856950 ms: Mark-Compact 4090.4 (4101.5) -> 4088.4 (4101.5) MB, pooled: 7.8 MB, 62.69 / 0.00 ms (average mu = 0.085, current mu = 0.014) allocation failure; scavenge might not succeed

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0x90b25b node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
2: 0xb979ca [node]
3: 0xdef715 [node]
4: 0xdf2e89 [node]
5: 0xe03498 [node]
6: 0xe02ddf [node]
7: 0x17965a7 [node]
8: 0xded261 [node]
9: 0xde1d77 [node]
10: 0xddf8bd [node]
11: 0xdbe066 [node]
12: 0x126a0c1 [node]
13: 0x7f673e63aeb6
Aborted (core dumped)
`

Command Code Version

0.23.1

Operating System

Linux

Terminal/IDE

N/A

Shell

bash

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions