Skip to content

Fix false-positive launch success for early-exiting processes#35

Merged
weter11 merged 3 commits intomainfrom
fix-false-positive-launch-success-17618267327832553973
Mar 18, 2026
Merged

Fix false-positive launch success for early-exiting processes#35
weter11 merged 3 commits intomainfrom
fix-false-positive-launch-success-17618267327832553973

Conversation

@weter11
Copy link
Owner

@weter11 weter11 commented Mar 17, 2026

This PR addresses an issue where SteamFlow would report a "Success" result even if the game process (Wine) exited immediately after spawning.

Changes include:

  1. Post-Spawn Verification: The launch pipeline now waits for a brief period (2 seconds) after spawning the process and polls its status. If the process has already exited, it is classified as a Failure with a failed_after_spawn status.
  2. Uncertain Launch Detection: If a process remains running but produces no log growth and no runtime graphics evidence (e.g., DXVK initialization), the result is marked as Uncertain.
  3. Improved Diagnostics: summary.json and the event log now include detailed verification metadata, such as process lifetime, exit code, and log growth observations.
  4. Validator Enhancements: The LaunchInvariantValidator now emits specific warnings (LAUNCH_EARLY_EXIT, LAUNCH_UNCERTAIN) to help users troubleshoot these cases.
  5. New Tests: Added integration-style tests using a mock runner to verify early exit and successful launch classification logic.

PR created automatically by Jules for task 17618267327832553973 started by @weter11

Introduces a post-spawn verification window to detect game processes that
exit immediately or fail to initialize correctly.

Key changes:
- Added `LaunchResult::Uncertain` and `LaunchVerification` diagnostics.
- Implemented a 2-second verification window in `LaunchPipeline`.
- Tracked log growth and graphics evidence to detect healthy vs uncertain launches.
- Added detailed warnings for `LAUNCH_EARLY_EXIT` and `LAUNCH_UNCERTAIN`.
- Included comprehensive tests for verification scenarios.

Co-authored-by: weter11 <14630689+weter11@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

google-labs-jules bot and others added 2 commits March 18, 2026 07:19
- Added a per-game NVAPI toggle to Graphics Settings.
- Improved runtime evidence collection to detect successful DXVK initialization.
- Implemented granular early-exit classification (e.g., "DXVK loaded but game exited early").
- Added prefix health checks to verify WINEPREFIX and user directories.
- Filtered non-fatal Wine warnings (winemac.drv) from strict graphics failure reports.
- Enhanced concise launch summaries with prefix and NVAPI metadata.

Co-authored-by: weter11 <14630689+weter11@users.noreply.github.com>
Treats D3D10 and D3D10.1 as capabilities satisfied by d3d10core, d3d11,
and dxgi when using the DXVK backend, rather than requiring literal
standalone DLL files.

Key changes:
- Introduced `DllProvider::Internal` for capability-satisfied DLLs.
- Implemented DXVK capability fixup in `ResolveDllProvidersStage`.
- Updated `build_dll_overrides` to allow builtin fallback for d3d10/d3d10_1.
- Improved validation error messages for missing D3D10 capabilities.
- Fixed launch result prioritization for degraded but failed launches.

Co-authored-by: weter11 <14630689+weter11@users.noreply.github.com>
@weter11 weter11 merged commit ad65563 into main Mar 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant