The forge's RSS is about 2.4 GiB against a first-hour mean of 965 MiB (#14264). Until #14283, the warning blamed one VM's "malloc", and the blamed VM changed from hour to hour (engine, pages, pipeline, tree). That figure was RSS minus that VM's own heap, so it pointed at nothing in particular. #14283 fixes how the growth is attributed but does not fix the growth.
Once #14283 is on main, read the /system minute lines and the needs-you sentence. They say whether the growth is in a named VM's JS heap or outside every heap (malloc, SQLite, native buffers). Find the owner and fix it.
What to look for when fixed:memory-growth stays out of the degraded list for a day.
The forge's RSS is about 2.4 GiB against a first-hour mean of 965 MiB (#14264). Until #14283, the warning blamed one VM's "malloc", and the blamed VM changed from hour to hour (engine, pages, pipeline, tree). That figure was RSS minus that VM's own heap, so it pointed at nothing in particular. #14283 fixes how the growth is attributed but does not fix the growth.
Once #14283 is on main, read the
/systemminute lines and the needs-you sentence. They say whether the growth is in a named VM's JS heap or outside every heap (malloc, SQLite, native buffers). Find the owner and fix it.What to look for when fixed:
memory-growthstays out of the degraded list for a day.