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
mouradhamoud opened this issue
Nov 24, 2016
· 4 comments
Labels
memoryIssues and PRs related to the memory management or memory footprint.processIssues and PRs related to the process subsystem.streamIssues and PRs related to the stream subsystem.
The text was updated successfully, but these errors were encountered:
mscdex
added
memory
Issues and PRs related to the memory management or memory footprint.
process
Issues and PRs related to the process subsystem.
stream
Issues and PRs related to the stream subsystem.
labels
Nov 24, 2016
Maybe this is related to how Node.js handles IO asynchronously, so it was not designed to handle this kind of code.
That is indeed what happens. The memory associated with the write-to-console request won't be freed until the next tick of the event loop. That next tick never happens in your code because it's executing an infinite loop.
memoryIssues and PRs related to the memory management or memory footprint.processIssues and PRs related to the process subsystem.streamIssues and PRs related to the stream subsystem.
Maybe this is related to how Node.js handles IO asynchronously, so it was not designed to handle this kind of code.
Execute the following:
or this code:
The node process starts eating memory (about 1.4 gigabyte in my case) and then it crashes with a heap out of memory error, see below:
The text was updated successfully, but these errors were encountered: