This issue seems to be reproducible 100% of the time, however it is hard to debug as it only seems to occur when a steam update is applied and I don't know of a way to reproduce the restart that happens on update.
The last time this happened, SFP failed to detect the launch arguments.
|
var cmdLine = GetCommandLine(); |
|
if (!cmdLine.Any()) |
|
{ |
|
Log.Logger.Error("Arguments are empty, cannot check arguments"); |
|
return false; |
|
} |
I think either SFP tries to get the command line of the process too soon after it starts, or during this update mechanism the process opens and restarts again too quickly so by the time SFP checks the arguments the process is no longer running.
This issue seems to be reproducible 100% of the time, however it is hard to debug as it only seems to occur when a steam update is applied and I don't know of a way to reproduce the restart that happens on update.
The last time this happened, SFP failed to detect the launch arguments.
SFP/SFP/Models/Steam.cs
Lines 361 to 366 in b13ac09
I think either SFP tries to get the command line of the process too soon after it starts, or during this update mechanism the process opens and restarts again too quickly so by the time SFP checks the arguments the process is no longer running.