Frysk creating a child process is a unique category of event. Unlike TaskObserver.Forked, the parent (frysk process) is not stopped. Unlike TaskObserver.Execed, the process wasn't seen to be created, and no opportunity to attach to the process was made available. Thoughts? If ok, assign back to me :-)
The situation is unique an observer specialized in frysk creating child processies would solve the problme.
Parent/child observers have been deleted - UI isn't using them - the interface got too complicated. If, in future feature becomes necessary a new bug can be created.