Skip to content

test-memory-usage failing on Windows #63210

Closed

Description

@aduh95

Test

test-memory-usage

Platform

Windows x64

Console output

failed 10 out of 10
not ok 678 parallel/test-memory-usage
  ---
  duration_ms: 223.00000
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/assert/utils:146
      throw error;
      ^
    
    AssertionError [ERR_ASSERTION]: 10506495 - 20737 === 10485760
    + actual - expected
    
    + 10485758
    - 10485760
            ^
    
        at Object.<anonymous> (d:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-memory-usage.js:47:10)
        at Module._compile (node:internal/modules/cjs/loader:1873:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:2013:10)
        at Module.load (node:internal/modules/cjs/loader:1596:32)
        at Module._load (node:internal/modules/cjs/loader:1398:12)
        at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
        at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
        at node:internal/main/run_main_module:33:47 {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: 10485758,
      expected: 10485760,
      operator: 'strictEqual',
      diff: 'simple'
    }
    
    Node.js v27.0.0-pre
  ...

Build links

Additional information

Not sure if flaky is the right term since it seems to fail 100% of the times

Activity

  1. added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    on May 9, 2026
  2. inoway46 commented on May 9, 2026

    @inoway46
    Contributor

    I opened #63214.

    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.

  3. StefanStojanovic commented on May 12, 2026

    @StefanStojanovic
    Contributor

    Closing the issue since #63220 landed through another PR, thus not triggering the closing mechanism

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    flaky-testIssues and PRs involving tests that fail intermittently in CI.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions