There is nothing there for the last 36+ hours.
I have tried updating WCG in BOINC, but still nothing more recent in that page.

There are only 5 entries there. Of them, 2 are errors from this computer. And both of them read like this:

Result Log

<core_client_version>5.10.7</core_client_version>
<![CDATA[
<message>
aborted by user
</message>
]]>

Surely they correspond to the last times I resetted or aborted the project.

Any news about this problem ? - The hpf application it still running amok on my Mac. This time I have described application reset and the application was not show running in the BOINC Manager but still used one complete CPU. Leave Application in Memory is activated.

The missing feedback is frustrating...

According to this problem I have to opt out it for all my systems. Is it posible to change the webserver, that the user can opt out/in project by the different venues ?

Sorry Lawrence, several hours later found i had not hit the Reply to Post button Here's what i concocted

@Dotsch

Each of the Device Profiles allows choosing different WCG projects.... this is how I've been running particular projects on specific machines. Word is that a further profile will be coming, making the total of mix-choices 5. The My Projects page overrides all device profile selections. Handy for multiple device owners / Farm managers.

With 'described' you may have meant 'prescribed'. Killing BOINC mgr will not kill the BOINC core client in many cases nor the science. Know next to nothing about MAC, but orphaning processes seems an issue. For HPF2 to restart there is an FAQ:

1. Suspend WCG completely in the Project Tab of BOINC mgr (not the Tasks Tab)
2. Wait 30 second
3. Unsuspend WCG in the Project Tab.

This has for many been the way to get HPF2 to resume at the last checkpoint and usually running to successful completion without further hitch.

Frustrating it is, but showing rarely and randomly on all OSses without any indication whatsoever, not even setting all debug flags have WCG techs been able to *will* a work unit into doing this, hence why the HPF2 was recently set to a reduced time-out of 6x the estimated flops given in the work-unit header. Anyone who can put a finger on what the cause is will be king in these quarters. Given that these work-units either run to end, without any error or were aborted destroying any track, my recommendation would be:

1. Set debug flags in cc_config.xml (See BOINC FAQ) specifically
<time_debug>1</time_debug>
<poll_debug>1</poll_debug>
<guirpc_debug>1</guirpc_debug>
<state_debug>1</state_debug>
<task_debug>1</task_debug>
<mem_usage_debug>1</mem_usage_debug>
2. Set the Checkpoint recorded flag
<checkpoint_debug>1</checkpoint_debug>
3. If it occurs, suspend the work-unit, not the entire project, so a new WU can start.
4. Report WU name, Checkpoint counts (message log), % progress, Run time, OS, CPU, RAM size, Swapfile size. (All contained at in the Message log beginning when starting BOINC)

I may have missed a flag.... experts are asked to add what more/less flags are needed.