Spawn Sunshine.exe in a job object, so it is terminated if SunshineSvc.exe dies #602
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This fixes an issue reported by DemonCat on Discord where SunshineSvc could not be restarted if it crashed or was forcefully terminated by the user. This happened because the now orphaned child Sunshine.exe held on to the handle to the log file that SunshineSvc created for it (which was being used as its
stdout
andstderr
).SunshineSvc doesn't have really any complicated logic post-startup, so the only real reason it's likely to die in the real world is if a user kills it to try to stop Sunshine. The current behavior of leaving Sunshine.exe running definitely isn't doing what the user wants, and doubly so if they can't even start SunshineSvc again afterwards.
Screenshot
Issues Fixed or Closed
Type of Change
.github/...
)Checklist
Branch Updates
LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.