Skip to content

RangeError: Set maximum size exceeded #142

Description

@adamraine
RangeError: Set maximum size exceeded
    at Set.add (<anonymous>)
    at Object.<anonymous> (/Users/asraine/src/clickup_frontend/node_modules/.pnpm/@memlab+core@2.0.0_typescript@6.0.2/node_modules/@memlab/core/dist/lib/HeapParser.js:71:17)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/asraine/src/clickup_frontend/node_modules/.pnpm/@memlab+core@2.0.0_typescript@6.0.2/node_modules/@memlab/core/dist/lib/HeapParser.js:15:58)
Error parsing heap snapshot
Please pass in a valid heap snapshot file

Node count in one of the heap snapshots is 16,997,604 which exceeds the maximum Set size of 16,777,216.

For context, this started happening after upgrading Chrome to M148 which seems to include a lot more nodes in heap snapshots. Assuming this is an intentional change with Chrome, I'm wondering if it's possible to use a different data structure that can accommodate larger node counts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions