Application freezes after returning from Lock screen

[usagirei]

Requirements

• This issue doesn't already exist
• This bug is Not related to compatability with a specific game

Summary

Borderless Gaming will freeze when you lock the computer screen, possibly in other scenarios that fit the same criteria.

Steps to reproduce

1. Run Application
2. Go to lock screen windows (Win+L), and wait a few moments (10~15 seconds should do it, if not lock it again and retry)
3. Come back to frozen application

Technical details

1. GetForegroundWindow may return NULL under certain conditions, one of which, is when the lock screen is active.

2. Then GetWindowThreadProcessId will return NULL too (Which happens to be a valid PID, the System Idle process) ,

3. Then when it tries to create a ProcessDetails class, for an invalid process, which tries to get the window title for an invalid window.
   

   Borderless-Gaming/BorderlessGaming.Logic/Windows/ForegroundManager.cs

   Lines 33 to 35 in 3cc4dc6

   	var handle = Native.GetForegroundWindow();
   	Native.GetWindowThreadProcessId(handle, out uint processId);
   	var details = new ProcessDetails(Process.GetProcessById((int)processId), handle);

4. It will then hang indefinitely trying to do so here:
   

   Borderless-Gaming/BorderlessGaming.Logic/Models/ProcessDetails.cs

   Lines 56 to 59 in 3cc4dc6

   	if (!Native.IsWindow(_windowHandle))
   	{
   	_windowHandle = Native.GetMainWindowForProcess(Proc).GetAwaiter().GetResult();
   	}

---

Checks for NULL/Invalid handles need to be introduced:

An early return here:

Borderless-Gaming/BorderlessGaming.Logic/Windows/ForegroundManager.cs

Line 33 in 3cc4dc6

var handle = Native.GetForegroundWindow();

var handle = Native.GetForegroundWindow(); 
if(handle == IntPtr.Zero) 
    return;

And maybe a short circuit here:

Borderless-Gaming/BorderlessGaming.Logic/Models/ProcessDetails.cs

Lines 56 to 59 in 3cc4dc6

	if (!Native.IsWindow(_windowHandle))
	{
	_windowHandle = Native.GetMainWindowForProcess(Proc).GetAwaiter().GetResult();
	}

if ((_windowHandle != IntPtr.Zero) && !Native.IsWindow(_windowHandle))
{
    _windowHandle = Native.GetMainWindowForProcess(Proc).GetAwaiter().GetResult();
}

Or ensure a ProcessDetails class can't be created for an invalid process/window

version

9.5.6.1328 - git 3cc4dc6