I have BOINC set to suspend processing when the computer is in use so that it will not conflict with people actually using the computers. Most BOINC projects follow this preference and pause computing when appropriate. However, the NWChem 0.11 (vbox64_t1) tasks do not. They continue running and using full CPU and RAM resources even though the BOINC client itself is suspended. This makes the computer completely unusable and will probably result in many participants like myself being unable to contribute resources to this project. The only way to resolve this is to manually kill the VBox processes in Task Manager (which also renders the results invalid) and that should not be necessary if the tasks are configured to follow the BOINC computing preferences.

I have BOINC set to suspend processing when the computer is in use so that it will not conflict with people actually using the computers. Most BOINC projects follow this preference and pause computing when appropriate. However, the NWChem 0.11 (vbox64_t1) tasks do not. They continue running and using full CPU and RAM resources even though the BOINC client itself is suspended. This makes the computer completely unusable and will probably result in many participants like myself being unable to contribute resources to this project. The only way to resolve this is to manually kill the VBox processes in Task Manager (which also renders the results invalid) and that should not be necessary if the tasks are configured to follow the BOINC computing preferences.

If you're running the long processes, it may take a while for the client to completely stop. My observations are that it could take up to a full 2 minutes before the client closes connection.
Probably the client stops right away, but is still performing garbage collection (or compress the data or so).


I do want to say that QuChempedIA LONG tasks, don't seem to honor the 600 minute timeout I have set in manager.
Some of the tasks were running past 11 hours non stop.

A delay of a few minutes would be annoying but not impossible to work with.

The problem is that the tasks in question did not EVER suspend even after hours of actively using the computer, or after manually suspending the entire BOINC manager.

I haven't seen the problem in the last week or two, so it was probably a temporary issue.

However, on our side there hasn't been any change for several weeks.