Skip to content

wasm-trace causes "heap out of memory" for big logs #3

@orestisfl

Description

@orestisfl

Issue is that the trace.write calls like this one:
https://github.com/wasm3/wasm-trace/blob/8f1aa89e811e221a83a89a6de806599d8df6f0cd/wasm-trace.js#L283
return false after a while and the whole output gets buffered. Eventually, node runs out of memory.

Node's memory can be increased with --max-old-space-size= but I've encountered situations where any size increase is eventually not enough.

As a solution, wasm-trace can wait for 'drain' events or can use a synchronised API like fs.writeSync.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions