Skip to content

JavaScript heap out of memory #5131

Closed as not planned
Closed as not planned

Description

@danielzgtg

Version

v25.6.0

Platform

Linux daniel-desktop3 6.17.0-12-generic nodejs/node#12-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan  9 20:46:52 UTC 2026 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

Run from danielzgtg/algora_analyzer@0440fb6 . The code was slightly modified after the crash.

How often does it reproduce? Is there a required condition?

Did not reproduce this issue beyond the first time it randomly occured

What is the expected behavior? Why is that the expected behavior?

It should not crash

What do you see instead?

$ ./main.js
[...]
Will fetch: https://api.github.com/repos/archestra-ai/archestra/issues/1301/comments?per_page=100&page=1
Response {
  status: 200,
  statusText: 'OK',
  headers: Headers {
    date: 'Tue, 17 Feb 2026 08:58:19 GMT',
    'content-type': 'application/json; charset=utf-8',
    'cache-control': 'public, max-age=60, s-maxage=60',
    vary: 'Accept,Accept-Encoding, Accept, X-Requested-With',
    etag: 'W/"REDACTED"',
    'x-github-media-type': 'github.v3; format=json',
    link: '<https://api.github.com/repositories/1020144870/issues/1301/comments?per_page=100&page=2>; rel="next", <https://api.github.com/repositories/1020144870/issues/1301/comments?per_page=100&page=2>; rel="last"',
    'x-github-api-version-selected': '2022-11-28',
    'access-control-expose-headers': 'ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset',
    'access-control-allow-origin': '*',
    'strict-transport-security': 'max-age=31536000; includeSubdomains; preload',
    'x-frame-options': 'deny',
    'x-content-type-options': 'nosniff',
    'x-xss-protection': '0',
    'referrer-policy': 'origin-when-cross-origin, strict-origin-when-cross-origin',
    'content-security-policy': "default-src 'none'",
    'content-encoding': 'gzip',
    server: 'github.com',
    'accept-ranges': 'bytes',
    'x-ratelimit-limit': '60',
    'x-ratelimit-remaining': '55',
    'x-ratelimit-reset': '1771322294',
    'x-ratelimit-resource': 'core',
    'x-ratelimit-used': '5',
    'transfer-encoding': 'chunked',
    'x-github-request-id': 'REDACTED'
  },
  body: ReadableStream { locked: false, state: 'readable', supportsBYOB: true },
  bodyUsed: false,
  ok: true,
  redirected: false,
  type: 'basic',
  url: 'https://api.github.com/repos/archestra-ai/archestra/issues/1301/comments?per_page=100&page=1'
}

<--- Last few GCs --->

[1505474:0x1a5c4000]    22012 ms: Mark-Compact (reduce) 4095.3 (4097.6) -> 4094.8 (4096.9) MB, pooled: 0.0 MB, 184.78 / 0.00 ms (+ 5.8 ms in 60 steps since start of marking, biggest step 3.6 ms, walltime since start of marking 199 ms) (average mu = 0.257,
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0x8f2d8b node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 2: 0xb6c71a  [node]
 3: 0xdbcaf5  [node]
 4: 0xdc0269  [node]
 5: 0xdd22a8  [node]
 6: 0xdd1bef  [node]
 7: 0x17640e7  [node]
 8: 0xdba641  [node]
 9: 0xdaf157  [node]
10: 0xdacc9d  [node]
11: 0xd75500  [node]
12: 0xd8dbc1  [node]
13: 0xb8a3a5 v8::String::NewFromTwoByte(v8::Isolate*, unsigned short const*, v8::NewStringType, int) [node]
14: 0xa72af9  [node]
15: 0x8ba5b4  [node]
16: 0x77317fdcfb4d 
Aborted (core dumped)

Additional information

No response

Activity

  1. transferred this issue fromnodejs/nodeon Feb 17, 2026
  2. avivkeller commented on Mar 21, 2026

    @avivkeller
    Member

    It's likely that your dependency is using too much memory, and thus, the issue should be reported there, not to Node.js

  3. danielzgtg commented on Mar 21, 2026

    @danielzgtg
    Author

    @avivkeller No, I don't have any dependencies. At that commit, I didn't have package.json either.

  4. avivkeller commented on Mar 21, 2026

    @avivkeller
    Member

    Whatever you are doing, it's using too much memory, causing the process to crash.

  5. avivkeller commented on Mar 21, 2026

    @avivkeller
    Member

    Did not reproduce this issue beyond the first time it randomly occured

    Your system was probably out of memory when you ran this. It's not reproducible, as you've said

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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