Parallel.Wait() is run into a deadlock if one of the worker run into a C5 error

[ToniKoehler]

If for some reasons one or more worker will crash and the parallelfox.exe will quit is work, the Parallel.Wait() will wait for that "busy" worker and don't recognize that the worker is dead.

[JoelLeach]

This is true. The user can press Ctrl+X to force exit the wait, but that is a hidden feature. It might be possible to modify Parallel.Wait() to check if the worker process/thread is still alive. C5 pops up a messagebox and the process doesn't close until the user presses OK, but it might still be helpful. I'm open to other ideas. The best solution is to figure out what is causing the C5 and prevent it. ;)

[ToniKoehler]

Hi Joel,
I have fixed that in my version of Parallelfox.vcx.
I will try to make a pull request with GIT, so you can check if my solution is your solution too. Because I normally work with VSS (old school boy), I need a little bit more time to be familiar with GIT. ;-)

[ToniKoehler]

Hi Joel,

now you can see 3 pull request:

1. parallelfox.vca based on branch v2.0 #14 | parallelfox.vca based on branch v2.0
   Bring the VCA (SourceSafe Textfile) up to date of your master-branche. So you can better compare with my other pull request.

2. CheckWorkerHealth in Parallel.Wait() to prevent deadlock #15 | CheckWorkerHealth in Parallel.Wait() to prevent deadlock
   These are the changes what prevent the deadlock on Parallel.Wait(), if one or more worker are dead.

3. New public variable gnParallelWorkernNum for better debugging and error handling #16 | New public variable gnParallelWorkernNum for better debugging and error handling
   This is nice to have. For me it's good to know which worker reports the error in case of DebugMode or hard errors. Also writes the _vfp.processid to _screen.caption.

Hope this helps you. I would be happy if I could contribute a small part to this great project. Thanks for your work!