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
mnpenner opened this issue
Jul 24, 2018
· 4 comments
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.memoryIssues and PRs related to the memory management or memory footprint.questionIssues that look for answers.
This has nothing to do with buffer. You can even remove the function entirely (just writing a simple static string in the loop) and the same problem will occur. Explicitly calling gc() after writing the string to stdout will allow the process to stay alive. Also, you can set --max-old-space-size=128 or something similarly lower to have it crash more quickly.
Ahah. Sorry. I tried removing as much code from my program while still reproducing the error, I guess I should have kept going.
I'm uncertain if this is a "bug" or not though. Shouldn't Node or V8 be monitoring how much memory is being consumed and perform some garbage collection before it runs out?
duplicateIssues and PRs that are duplicates of other issues or PRs.memoryIssues and PRs related to the memory management or memory footprint.questionIssues that look for answers.
Node is crashing with this error:
With this code:
I could be wrong, but since I'm not actually holding onto any of those buffers, I believe Node or V8 should be cleaning up that memory for me.
It takes about 40-65 seconds to exhaust the memory.
The text was updated successfully, but these errors were encountered: