You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The failure is off by 2 bytes (10485758 vs 10485760), which suggests the 10 MiB ArrayBuffer allocation is being tracked, but some unrelated ArrayBuffer/Buffer memory may be getting freed between the two process.memoryUsage() snapshots.
The PR keeps the strict arrayBuffers delta check and calls gc() before taking the baseline to reduce that chance.
If that is not enough to make the exact delta stable, another option would be to relax the assertion to allow small unrelated ArrayBuffer cleanup between the snapshots.
Activity
inoway46 commentedon May 9, 2026
I opened #63214.
The failure is off by 2 bytes (
10485758vs10485760), which suggests the 10 MiBArrayBufferallocation is being tracked, but some unrelated ArrayBuffer/Buffer memory may be getting freed between the twoprocess.memoryUsage()snapshots.The PR keeps the strict
arrayBuffersdelta check and callsgc()before taking the baseline to reduce that chance.If that is not enough to make the exact delta stable, another option would be to relax the assertion to allow small unrelated ArrayBuffer cleanup between the snapshots.
StefanStojanovic commentedon May 12, 2026
Closing the issue since #63220 landed through another PR, thus not triggering the closing mechanism