Hello,
These processes are due to the new integration testing process. This new process was introduced in Pharo 3.0 alpha, and we found the bug and fixed it.��
Recently we backport the new integration process to Pharo 2.0 and seemingly it created the same bug but since we read your mail we were not aware of it. We need to backport the fix.
We will fix that within a few days.
As a workaround, you can just kill these processes in your image for now ...
Thanks for reporting the issue,