Linux Builder Play discards early startup diagnostics #2022

Closed

opened 2026-11-10 23:56:06 +00:00 by Arkex-ai · 0 comments

Arkex-ai commented

2026-11-10 23:56:06 +00:00

(Migrated from github.com)

When Linux Builder starts a game through its Play button, it redirects both child streams to /dev/null. If the child exits before its application log contains the cause, the startup diagnostic is lost. This came up during triage of #1984, whose crash remains a separate investigation.

On Linux (WSL Ubuntu), I ran the current play() function with a synthetic executable. It exited 73 with no retained output. The same executable invoked directly also exited 73 and printed its expected marker on stderr.

I'll take the diagnostic path. Keep the game detached, retain a bounded local startup log, and preserve direct terminal behavior. S3, Linux Builder only, affected share unknown, confidence 1.0 for the synthetic reproduction. Claim in #dev-work.

When Linux Builder starts a game through its Play button, it redirects both child streams to `/dev/null`. If the child exits before its application log contains the cause, the startup diagnostic is lost. This came up during triage of #1984, whose crash remains a separate investigation. On Linux (WSL Ubuntu), I ran the current `play()` function with a synthetic executable. It exited 73 with no retained output. The same executable invoked directly also exited 73 and printed its expected marker on stderr. I'll take the diagnostic path. Keep the game detached, retain a bounded local startup log, and preserve direct terminal behavior. S3, Linux Builder only, affected share unknown, confidence 1.0 for the synthetic reproduction. [Claim in #dev-work](https://discord.com/channels/1568810484818378804/1569019786766188665/1569863170951225364).

Commenting is not possible because the repository is archived.