Version
26.1.0
Platform
Subsystem
No response
What steps will reproduce the bug?
Seems Node 25 vs 26 regression and garbage collector not working properly for arrayBuffers?
Any microservice what do ETL of big buffers picture:
Node 26:
{
"rss": 1163239424,
"external": 4308786,
"heapUsed": 70688576,
"heapTotal": 75517952,
"arrayBuffers": 1006123399 // huge leaking here
}
Node 25:
{
"rss": 398155776,
"external": 260510278,
"heapUsed": 47046268,
"heapTotal": 51511296,
"arrayBuffers": 257421783 // all fine, GC works in predictable way
}
How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
GC should works in predictable way for Node.js 26 too, not only Node.js 25
What do you see instead?
See huge RAM leaking for arrayBuffers especially
Additional information
No response
Version
26.1.0
Platform
Subsystem
No response
What steps will reproduce the bug?
Seems Node 25 vs 26 regression and garbage collector not working properly for arrayBuffers?
Any microservice what do ETL of big buffers picture:
Node 26:
{ "rss": 1163239424, "external": 4308786, "heapUsed": 70688576, "heapTotal": 75517952, "arrayBuffers": 1006123399 // huge leaking here }Node 25:
{ "rss": 398155776, "external": 260510278, "heapUsed": 47046268, "heapTotal": 51511296, "arrayBuffers": 257421783 // all fine, GC works in predictable way }How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
GC should works in predictable way for Node.js 26 too, not only Node.js 25
What do you see instead?
See huge RAM leaking for
arrayBuffersespeciallyAdditional information
No response