For now, the crashed process is gone, it will be hidden in Process Lasso, and also Windows Task Manager.
But the log still spamming inside the log, I wonder which Windows 10 update has changed this behave, and why MS choose to hide the crashed process, so you can't kill it manually.
So the only ways that left is just close Process Lasso...
And ya, I think this issues should be fixed, but not hide the log, because it has becoming worst.
It is not hanging on this state anymore...
The cause is a logging anomaly when a process is in the in-between state of crashing, during the crash dialog or 'Windows is searching for solutions' dialog.
So it is not a simple logging anomaly, the process is indeed crashed, and it should be exit, but instead that, it is still hidden and "running", you can't run the same *.exe anymore.
You also can't do any delete or modify on the *.exe, because it is still "running".
So, unless you close/restart Process Lasso, or you will having more and more crashed "running" process being hidden in the darkness...
PS: I found this when I written a c++ program that somehow the compiler accept my if loop mistake and running for crashing.
PS2: It should be fine for program that design to running more than 1 process, but it is still not good for biting the memory.