If the BOINC client suspends the MM application for whatever reason, such as because it got another higher priority WU from another project, even with suspending to memory enabled, when its turn to run comes up again, a new MM application is launched and the previous one becomes a zombie.

Eventually, a system collects several such zombie MM applications in memory, unbeknown to the BOINC client, which does not report the zombie MM application and returns the WU crunched by the new instance.

I've only observed this on Windows, but I cannot say that it does not happen on Linux too.

TIA

____________