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

[Feli87]

Confirm this is a Node library issue and not an underlying OpenAI API issue

• This is an issue with the Node library

Describe the bug

When updating to the latest SDK version 6.0.2 the application stopped compiling, complex types of 12gb to compile. ???

To Reproduce

...

Code snippets

71.1 
171.1 <--- Last few GCs --->
171.1 
171.1 [20:0x2ffa5000]   167081 ms: Mark-Compact 4039.8 (4128.1) -> 4024.0 (4128.6) MB, pooled: 3 MB, 2758.43 / 0.00 ms  (average mu = 0.133, current mu = 0.086) allocation failure; scavenge might not succeed
171.1 [20:0x2ffa5000]   170489 ms: Mark-Compact 4040.1 (4128.6) -> 4024.6 (4129.1) MB, pooled: 2 MB, 3377.93 / 0.00 ms  (average mu = 0.070, current mu = 0.009) allocation failure; scavenge might not succeed
171.1 
171.1 
171.1 <--- JS stacktrace --->
171.1 
171.1 FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
171.1 ----- Native stack trace -----
171.1 
171.1  1: 0xe16044 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
171.1  2: 0x11e0dd0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
171.1  3: 0x11e10a7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
171.1  4: 0x140e985  [node]
171.1  5: 0x140e9b3  [node]
171.1  6: 0x1427a8a  [node]
171.1  7: 0x142ac58  [node]
171.1  8: 0x1c90921  [node]
172.2 Aborted (core dumped)
------
failed to solve: process "/bin/sh -c NODE_OPTIONS=\"--max-old-space-size=4096\" npm run build" did not complete successfully: exit code: 134

OS

Linux

Node version

v22.5.1

Library version

openai 6.0.2

[RobertCraigie]

Can you share any details about your setup? What is npm run build doing?

[Feli87]

Can you share any details about your setup? What is npm run build doing?

I am using NestJS inside Docker. If I switch to SWC, the build is much faster, but I need to reconfigure modules due to circular dependency issues. If I stay with TypeScript, the build never finishes, even after increasing available memory.

FROM node:22.17.1-bullseye

Increasing memory helps a bit but the build still crashes

RUN NODE_OPTIONS="--max-old-space-size=8192" npm run build

The more RAM I assign, the further the compilation goes, but it eventually crashes anyway.

but work -> OpenAI 5.20

Dependencies snapshot (partial):

NestJS 11.x (@nestjs/core, @nestjs/platform-fastify, @nestjs/graphql, etc.)

Prisma 6.13

BullMQ 5.41

Fastify 5.x

GraphQL 16.9

LangChain 0.3.33

OpenAI 6.2.0

AWS SDK v3 (@aws-sdk/client-s3, @aws-sdk/client-cloudwatch, etc.)

Redis (ioredis, @socket.io/redis-adapter)

Others: mongoose, argon2, bcrypt, rxjs, winston, zod

DevDependencies:

TypeScript 5.9.2

SWC (@swc/core, @swc/jest)

Jest 30.x

ESLint + Prettier

Prisma CLI

Typedoc

[juliogoldbach-tw]

When updating to the latest SDK version 6.0.2 the application stopped compiling, complex types of 12gb to compile. ???`
Library version
openai 6.0.2

I think you mean v6.2.0 @Feli87
I am also experiencing the same issue with typescript

[Feli87]

When updating to the latest SDK version 6.0.2 the application stopped compiling, complex types of 12gb to compile. ???`
Library version
openai 6.0.2

I think you mean v6.2.0 @Feli87 I am also experiencing the same issue with typescript

Yes... I had to stay on beta version 5.20 because I couldn’t update—it doesn’t compile. Luckily, everything is still working with the Response API.