Skip to content
Builds on builder-uwqkzv crash in next build with "invalid table size" since Oct 1 ~11:00 UTC
leothesen
OP

2 months ago

Since about 11:14 UTC on 2026-10-01, every build of our service that lands on builder-uwqkzv crashes about 9 seconds into next build. The same code builds fine on a different builder.

Error (identical on every failed build):

Creating an optimized production build ...

[55:0x425b0000] 8982 ms: Scavenge (interleaved) 1310.5 (1347.9) -> 1310.5 (1347.9) MB ... allocation failure;

FATAL ERROR: invalid table size Allocation failed - JavaScript heap out of memory

5: v8::internal::HashTable<v8::internal::NumberDictionary, ...>::Shrink

9: v8::internal::JSObject::AddDataElement

12: v8::internal::Runtime_CreateDataProperty

Next.js build worker exited with code: null and signal: SIGABRT

This is not an ordinary out-of-memory: the heap is only ~1.3 GB when it dies. V8 is overflowing a single object's integer-keyed dictionary.

Which builder each build ran on (environment "dev", service "@teiken/internal"):

03f334af builder-uwqkzv OK (08:32 UTC)

8f634f85 builder-uwqkzv OK (09:28 UTC)

5aad6c0c builder-uwqkzv CRASH (11:14 UTC)

937770ba builder-uwqkzv CRASH

0f968cc0 builder-uwqkzv CRASH

ce953877 builder-uwqkzv CRASH

ef411d37 builder-uwqkzv CRASH (built with NO_CACHE=1, so not a stale build cache)

0a34aab7 builder-ychywe OK (17:58 UTC, already contains every commit from the first failure)

2d81878d builder-uwqkzv CRASH (19:06 UTC)

What we ruled out:

  • Our code: the failing commits build cleanly on local macOS and on linux/amd64 in Docker, with the same Node 22.23.2, Next.js 15.5.27 and pnpm 10.10.0.
  • Build cache: still crashes with NO_CACHE=1.
  • Builder image: the same railpack-v0.40.1 / mise-2026.9.15 on both the passing and failing builds.

Could you check builder-uwqkzv, or move this service's builds off it? Every build of this service has landed on it except one, so a retry doesn't help.

Solved$10 Bounty

Pinned Solution

leothesen
OP

a month ago

Sorted with support. builder-uwqkzv was the problem all along. And it's been taken out of rotation.

5 Replies

Status changed to Awaiting Railway Response Railway • about 2 months ago


2 months ago

We don't use JavaScript anywhere in our build infrastructure; that error would occur at the application level on your end.


Status changed to Awaiting User Response Railway • about 2 months ago


Railway
BOT

2 months ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 2 months ago


Try to set the variable NEXT_PRIVATE_MAX_WORKERS=4 as this will limit how many workers spawned by the next build command to avoid V8's dictionary limits. You can also try to set experimental.webpackBuildWorker = false in your next.config.ts as a workaround.


leothesen
OP

2 months ago

Update: a controlled test

We rebuilt the exact commit that last built successfully, straight from GitHub:

  • Oct 1, 09:28 UTC: commit 0515de51 on builder-uwqkzv (8f634f85): ✅ built
  • Oct 5: the same commit 0515de51 on builder-uwqkzv (cd3cc1fe): ❌ invalid table size

Same commit, same lockfile, same builder. Nothing in our repo can explain the change, so something in the build environment changed between ~09:30 and ~11:14 UTC on Oct 1, and it's still in effect.

What we're asking

  1. What changed on builder-uwqkzv, or the Railpack/mise images it uses, in that window?
  2. Could you route this service's builds to a different builder, so we can confirm and get unblocked?

leothesen
OP

2 months ago

Update: our dev builds are succeeding again, now that they're landing on other builders:

  • d902638b: builder-ychywe, compiled successfully
  • 7c59958e: builder-ockslp, compiled successfully

Thanks! Could you confirm whether builder-uwqkzv was taken out of rotation or fixed? If it's still in service, our builds will fail the same way if they land on it again.


leothesen
OP

a month ago

Sorted with support. builder-uwqkzv was the problem all along. And it's been taken out of rotation.


Status changed to Solved dev • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...