Nothing worse than fixing a memory leak in NodeJs. UGH!

  • 2
    a real devRant worthy rant!
    So what happened and how?
  • 4
    Not fixing it?
  • 2
    @heyheni Its a streaming issue, we have audio data being streamed into NodeJs for some processing. I have being monitoring it with the devtools and the heap memory seems to be stable. It releases the data after a stream is over. BUT somehow, there is a native memory leak. The overall node process still keeps the memory and does not release it! :(
  • 0
    @electrineer Have to! But im lost!
  • 1
    Fix a bug in XTerm.
  • 3
    Locks, file handles, and streams, oh my!

    Monitor using internal counters - external tools will not help tracking down who holds the memory.
    Smart Money is on the audio native lib keeping its buffers alive.
  • 2
    These are the kinds of node JS rants I wanna see. Keep us updated 👌
Add Comment