Process Monitor

[mirkobrombin]

There are 2 scenarios where we could need to keep monitoring the status of a process:

• the client could show an icon to tell the user an application is still running
• the server could finish an operation when a process stop running
• the agent (WineBridge) could send an information once a process stop running

So what we need are 3 functions:

• StartProcessMonitor
• PingProcessMonitor
• StopProcessMonitor

[cyberphantom52]

What exactly do we expect StartProcessMonitor to do/return. It'll help with the implementation if i knew the details in advance.

[mirkobrombin]

Here's a more detailed explanation:

WineBridge runs inside a Wine prefix and uses Windows APIs to launch and manage Windows processes. When we start a process (using CreateProcess or similar), we get a process handle or at least a process ID. What we need is to monitor that process from inside Wine, using Windows APIs.

So, basically:

• StartProcessMonitor(processId: number)
  This function should start a background monitor (thread, timer, or event-based) that waits for the process to exit (e.g., using WaitForSingleObject, GetExitCodeProcess, or similar). It returns a unique monitor ID (or just the processId again if it's enough) that we can use to ping or stop the monitor. It doesn’t block, just sets up the monitoring.

• PingProcessMonitor(monitorId: number)
  This is called from the server/client to check if the process is still running. It returns a status: running, exited, maybe even the exit code if available.

• StopProcessMonitor(monitorId: number)
  Stops the monitoring and releases any resources.

The goal is to detect when the process exits from inside Wine using the Windows API. The client and server can then query this status via gRPC and react accordingly (UI updates, cleanup, etc.).