BugId occasionally hangs when a child process is invoked

[maxcoderrrr]

I noticed that sometimes BugId (tested with the latest version) gets stuck when the main application process invokes a child process. However, I am not able to reproduce this issue deterministically - it occurs occasionally only and seems to be random.

Here is an example output when I invoke the same command twice, without any changes between them:

C:\Python311\python.exe BugId.py "C:\test\foo.exe" -- "C:\test2\foo.bar"
┌───[ Warning ]────────────────────────────────────────────────────────────────────────────────────────────────────────
│ You are running a newer version of Python (3.11.4) in which this version of
│ BugId has not been tested yet.
│ The following Python versions have been tested:
│   3.8.5, 3.9.1, 3.9.7, 3.10.0, and 3.11.1.
│ Please report this so BugId can be tested with this version of Python at the following URL:
│   https://github.com/SkyLined/BugId/issues/new
└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
┌───[ Software license warning ]───────────────────────────────────────────────────────────────────────────────────────
│ ▲ You have no license for BugId and your trial period will expire on August 9th, 2023
│ ▲ You have no license for mBugId and your trial period will expire on August 9th, 2023
└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
→ Command line: C:\test\foo.exe C:\test2\foo.bar
+ Main process 4304/0x10D0 (foo.exe, x64, IL:3): Attached ("C:\test\foo.exe" C:\test2\foo.bar).
+ Sub process 15012/0x3AA4 (sub.exe, x64, IL:3): Attached ("C:\test\sub.exe" "C:\test" test3 test4).
- Sub process 15012/0x3AA4 (sub.exe, x64, IL:3): Terminated.
[hangs and doesn't continue from here]

Second run:

C:\Python311\python.exe BugId.py "C:\test\foo.exe" -- "C:\test2\foo.bar"
┌───[ Warning ]──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ You are running a newer version of Python (3.11.4) in which this version of
│ BugId has not been tested yet.
│ The following Python versions have been tested:
│   3.8.5, 3.9.1, 3.9.7, 3.10.0, and 3.11.1.
│ Please report this so BugId can be tested with this version of Python at the following URL:
│   https://github.com/SkyLined/BugId/issues/new
└────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
┌───[ Software license warning ]─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ ▲ You have no license for BugId and your trial period will expire on August 9th, 2023
│ ▲ You have no license for mBugId and your trial period will expire on August 9th, 2023
└────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
→ Command line: C:\test\foo.exe C:\test2\foo.bar
+ Main process 2844/0xB1C (foo.exe, x64, IL:3): Attached ("C:\test\foo.exe" C:\test2\foo.bar).
+ Sub process 8892/0x22BC (sub.exe, x64, IL:3): Attached ("C:\test\sub.exe" "C:\test" test3 test4).
- Sub process 8892/0x22BC (sub.exe, x64, IL:3): Terminated.
» T+0.3 executing command gh; (Running application)...
[snip]

So in the second run it doesn't hang and continues as expected. The command line and environment between the runs are the same.

As a side note, I don't think it's related to the Python warning, as I experienced the same issue with Python versions that have been previously tested (i.e., 3.11.1). The problem occurs whether PageHeap is completely disabled, enabled or partially enabled (such as only for the main process, or only for the child process). I don't think it is related to specific inputs either.

Is this a known issue or is there a possible workaround? It looks very similar to this issue reported previously:
#105

Adding a timeout parameter (n0ApplicationMaxRunTimeInSeconds) does not resolve this issue as a potential workaround.

The way I typically notice this is when I try to run BugId over say 10 input files in a queue, and when I check the status of it, it got stuck in one of the cases because of this.