Skip to main content
Corvus Connection

Resource use

Corvus Connection runs beside a game, a capture app, a face tracker, and whatever else your stream needs. It is built to hand memory back when you are not looking at it, and it keeps working the whole time it sits in the tray. This page explains what it holds while you work, what each way of putting it away releases, and the figures we measured.

  • Where the memory goes

    Most of the app is light. Two parts are not, and both belong to the script editor: the browser engine that draws the editor, and the C# language service that gives you completions, live errors, and the rest of the editing help.That means the heaviest number on this page is a session with the script editor open. A session that never opens it stays noticeably smaller, and the parts that answer chat, run your flows, and drive your overlays are a small share of the total either way.

  • Minimize to the tray

    Minimizing puts the script editor to sleep. Its browser engine stops running timers and animations, and the memory it was holding goes back to Windows for your game to use. Around 400 MB of active memory is returned this way.The editor itself stays loaded, along with anything you have not saved, so bringing the window back is instant. This is the right choice when you are stepping away for a few minutes.

  • Close to the tray

    Closing the window goes further. The editor releases its browser engine completely, the C# language service parks the script you had open, and the app compacts what is left. Your work is saved and your place in the file is remembered first.Coming back takes a short pause while the editor reloads, which is the trade for the larger saving. Close to the tray when you are settling in for a long session in a game.

  • It keeps running either way

    Putting the window away never puts your stream on hold. Chat commands still answer, flows still run, overlays still update, and connected accounts stay signed in. Only the parts you were looking at are released, and the app deliberately stays at full speed in the background rather than being throttled by Windows.

  • What we measured

    App state
    Memory
    Coming back
    Window in front, script editor open
    about 1.3 GB
    n/a
    Minimized to the tray
    about 400 MB of active memory returned to Windows
    instant
    Closed to the tray
    about 650 MB
    a short pause while the editor reloads
    • App state
      Window in front, script editor open
      Memory
      about 1.3 GB
      Coming back
      n/a
    • App state
      Minimized to the tray
      Memory
      about 400 MB of active memory returned to Windows
      Coming back
      instant
    • App state
      Closed to the tray
      Memory
      about 650 MB
      Coming back
      a short pause while the editor reloads
    Measured on one Windows PC, with the script editor open and a script loaded, which is the heaviest the app gets. Treat these as a shape rather than a promise: your figures will differ with your hardware, your integrations, and what you have open. We will refresh them against each release.

  • If the app is still too heavy for your setup

    • Close to the tray instead of minimizing before you start a demanding game. It is the larger saving by a wide margin.
    • Leave the script editor closed when you are not editing. Reaching it is one click when you need it, and skipping it keeps the biggest two costs off your machine.
    • Tell us. Memory pressure on a loaded streaming PC is a bug worth hearing about, and the security page has the address to reach us at.