We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
trace.write
false
Node's memory can be increased with --max-old-space-size= but I've encountered situations where any size increase is eventually not enough.
--max-old-space-size=
As a solution, wasm-trace can wait for 'drain' events or can use a synchronised API like fs.writeSync.
wasm-trace
fs.writeSync
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue is that the
trace.writecalls like this one:https://github.com/wasm3/wasm-trace/blob/8f1aa89e811e221a83a89a6de806599d8df6f0cd/wasm-trace.js#L283
return
falseafter 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-tracecan wait for 'drain' events or can use a synchronised API likefs.writeSync.The text was updated successfully, but these errors were encountered: