Why does RSS constantly grow when reading data from a child process and calling process.stdout.write()?

This page summarizes the projects mentioned and recommended in the original post on reddit.com/r/node
#JavaScript #NodeJS #Linux #native-messaging #file-api

Our great sponsors
  • Appwrite - The Open Source Firebase alternative introduces iOS support
  • InfluxDB - Access the most powerful time series database as a service
  • Sonar - Write Clean JavaScript Code. Always.
Our great sponsors

  • node

    Node.js JavaScript runtime :sparkles::turtle::rocket::sparkles:

    I don't know how node is processing the stream and buffering or not buffering. I just invested the past few hours into researching Node.js buffering and not buffering read(). There are more than one issue regarding the subject-matter, e.g., https://github.com/nodejs/node/issues/2972, https://github.com/nodejs/node-v0.x-archive/issues/4000, https://github.com/nodejs/node/issues/6379. From what I gather Node.js blames the process itself. However, I run the same algorithm using Python, C++, C, QuickJS JavaScript engine where the RSS does not exponentially increase during usage.

  • captureSystemAudio

    Capture system audio ("What-U-Hear")

    The Node.js Native Messaging host creates a child process and streams captured system audio to the browser https://github.com/guest271314/captureSystemAudio/blob/master/native_messaging/capture_system_audio/capture_system_audio_node.js.

  • Appwrite

    Appwrite - The Open Source Firebase alternative introduces iOS support . Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!

  • native-messaging

    Native Messaging Host Protocol for Browser Extensions

    // Node.js Native Messaging host // https://github.com/simov/native-messaging/blob/master/protocol.js // https://github.com/simov/native-messaging/blob/master/nodejs/example.js // Might be good to use an explicit path to node on the shebang line // in case it isn't in PATH when launched by Chrome process.stdin.on('readable', () => { let input = []; let chunk; while ((chunk = process.stdin.read())) { input.push(chunk); } input = Buffer.concat(input); const msgLen = input.readUInt32LE(0); const dataLen = msgLen + 4; if (input.length >= dataLen) { const content = input.slice(4, dataLen); const json = JSON.parse(content.toString()); handleMessage(json); } });

  • node-v0.x-archive

    Moved to https://github.com/nodejs/node

    I don't know how node is processing the stream and buffering or not buffering. I just invested the past few hours into researching Node.js buffering and not buffering read(). There are more than one issue regarding the subject-matter, e.g., https://github.com/nodejs/node/issues/2972, https://github.com/nodejs/node-v0.x-archive/issues/4000, https://github.com/nodejs/node/issues/6379. From what I gather Node.js blames the process itself. However, I run the same algorithm using Python, C++, C, QuickJS JavaScript engine where the RSS does not exponentially increase during usage.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts