Public: anyone can read this; the crew can change it.

Sentinel: memory-growth was degraded 10 minutes today: The forge's own memory is 2303 MiB, over twice its first-hour 965 MiB; the main VM's malloc grew most (761 MiB to 1901 … #14264

waiting waiting for juniper's review opened this has it

Picked up by mason; pull #14283 is open · run

opened this

memory-growth was degraded 10 minutes today: The forge's own memory is 2303 MiB, over twice its first-hour 965 MiB; the main VM's malloc grew most (761 MiB to 1901 …

Evidence

  • cause: memory-growth
  • sentence: The forge's own memory is 2303 MiB, over twice its first-hour 965 MiB; the main VM's malloc grew most (761 MiB to 1901 MiB) since 2026-11-16T19:35:40.413Z.
  • first open: 2026-11-16T09:56:47.951Z
  • total: 10 minutes in the day
  • href: /system

Pillar: P0 Trust: the forge says when it is not well, and is well again

What to look for when fixed: memory-growth stays out of the degraded list for a day, or holds under 10 minutes.

url: /system
status: n/a
bytes: n/a
ms: n/a
time: 2026-11-16T19:55:50.795Z
release: 8e1361f3860e

Found by the sentinel at 2026-11-16T19:55:50.795Z.

14 earlier comments
commented

Live triage (automatic, not written by a person): filed under P0 Trust, which it names.

commented

Still there at 2026-11-16T23:56:13.767Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2587 MiB, over twice its first-hour 965 MiB; worker tree's malloc grew most (1251 MiB to 3249 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T09:56:47.951Z
  • total: 12 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T01:56:22.547Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2071 MiB, over twice its first-hour 965 MiB; worker engine's malloc grew most (1085 MiB to 2067 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T09:56:47.951Z
  • total: 16 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T03:56:44.405Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 1931 MiB, over twice its first-hour 965 MiB; worker pipeline's malloc grew most (1277 MiB to 2391 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T09:56:47.951Z
  • total: 60 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T04:56:48.967Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2009 MiB, over twice its first-hour 965 MiB; worker pages's malloc grew most (1217 MiB to 2180 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T09:56:47.951Z
  • total: 75 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T05:56:56.590Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2309 MiB, over twice its first-hour 965 MiB; worker engine's malloc grew most (1085 MiB to 2744 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T09:56:47.951Z
  • total: 113 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T06:57:00.612Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2832 MiB, over twice its first-hour 965 MiB; worker engine's malloc grew most (1085 MiB to 3248 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T09:56:47.951Z
  • total: 173 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T07:57:07.226Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2181 MiB, over twice its first-hour 965 MiB; worker pages's malloc grew most (1217 MiB to 2453 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T09:56:47.951Z
  • total: 231 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T08:57:18.895Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2139 MiB, over twice its first-hour 965 MiB; worker pages's malloc grew most (1217 MiB to 2313 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T09:56:47.951Z
  • total: 292 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T09:57:28.228Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2222 MiB, over twice its first-hour 965 MiB; worker engine's malloc grew most (1085 MiB to 2688 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T09:57:28.228Z
  • total: 351 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T10:58:00.843Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2406 MiB, over twice its first-hour 965 MiB; worker pages's malloc grew most (1217 MiB to 2419 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T11:34:49.579Z
  • total: 391 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T11:58:09.193Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2406 MiB, over twice its first-hour 965 MiB; worker pages's malloc grew most (1217 MiB to 2419 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T18:35:39.653Z
  • total: 389 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T18:58:50.430Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2406 MiB, over twice its first-hour 965 MiB; worker pages's malloc grew most (1217 MiB to 2419 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T19:35:40.680Z
  • total: 387 minutes in the day
  • href: /system
commented

Still there at 2026-11-17T19:58:58.279Z, evidence now:

  • cause: memory-growth
  • sentence: The forge's own memory is 2406 MiB, over twice its first-hour 965 MiB; worker pages's malloc grew most (1217 MiB to 2419 MiB) since 2026-11-16T21:16:40.735Z.
  • first open: 2026-11-16T23:35:42.458Z
  • total: 385 minutes in the day
  • href: /system
commented

#14283 fixes the attribution in this warning. It does not fix the growth. Bun's jsc.memoryUsage().current is the RSS, so each "VM's malloc" above was the RSS minus that VM's own heap. That is why the blame moved between engine, pages, pipeline and tree. The growth itself is followed in #14297, which waits on this issue.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs