Fix huge memory waste in IpcMain.Once [IMPORTANT] #833
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My app uses

IpcMain.Once
to wait for an "all good, next frame" message from the front end. It's updating data at rates well over 60fps, so I'm callingIpcMain.Once
a lot. I noticed that since I started doing this, my memory usage went waaay up (from 40-50Mb to about 800Mb), so I started investigating memory dumps, and indeed, I found this object:Which I later traced to be the object holding all of the socket listeners.
To fix this issue, all I had to do was replace the
Socket.On
inIpcMain.Once
withSocket.Once<object>
, and my memory usage went back down to 40-50Mb.