Hello,

I had a work unit https://gpugrid.net/workunit.php?wuid=29624565 that was displaying as "running" but after minutes it didn't made any progress: neither in percentage nor in elapsed time.


So I had to cancel my task https://gpugrid.net/result.php?resultid=36261497.

Did this happen to someone else? I tried to suspend and resume it without success. Is there a way to "force restart" a task?

This task was then later correctly completed by someone else which is on Linux while I'm on Windows, could that explain?

with this type of task, it takes several minutes until you can see progess in the BOINC Manager. So just be patient. Also, it takes a short while until the GPU starts it's work.
Suspending these tasks will kill them. So don't do it. Just let it run, and be patient :-)

with this type of task, it takes several minutes until you can see progess in the BOINC Manager.

Also, it takes a short while until the GPU starts it's work.

Suspending these tasks will kill them. So don't do it. Just let it run, and be patient :-)

So it looks like there is in fact a bug.

I have this work unit: https://gpugrid.net/workunit.php?wuid=29641527

It went successfully to 10%. But then I suspended it manually (to play some games) and then I resumed it, but now it's been 30 minutes that it is like this (UI is in french):


(image link: https://imgur.com/a/1LCD3Hr)

The task resumes correctly (to 0%) on the following scenario though:
- Computer suspend
- Computer off/on
- Paused because there is a high priority application running

I tried to suspend my computer and restart it, but it looks like it didn't start the task yet (5 minutes after).

Is there any log I could provide to help debug this?

So I just restarted my computer and the task started directly!

I am not sure whether this is a BOINC or a GPUGRID bug though.

So I just restarted my computer and the task started directly!

I am not sure whether this is a BOINC or a GPUGRID bug though.

make your choce in the BOINC Manager: "Options" > "Other settings"

It probably depends on what else is running under the control of the BOINC client on that machine.

When you 'unsuspend' a task, you are merely giving permission for it to run when a resource of the specified type becomes available. If at that moment, your GPUS are busy on other projects' tasks, the GPUGrid tasks will simply be left on one side.

It probably depends on what else is running under the control of the BOINC client on that machine.

When you 'unsuspend' a task, you are merely giving permission for it to run when a resource of the specified type becomes available. If at that moment, your GPUS are busy on other projects' tasks, the GPUGrid tasks will simply be left on one side.

I'm running on a laptop and had to turn off going to sleep even on battery. I didn't read the entire thread so I could be missing something. I also set on the activity tab to run gpu and cpu always. I also set liberal controls on the web gpugrid settings page. For example use at most 100% of everything and don't suspend for any reason. I'd suggest opening the floodgates for gpugrid and see if it changes anything.

I haven't noticed any thread about process monitors but I use HWiNFO64. That might shed light on heat issues that throttle processing.

So I opened an issue on BOINC GitHub's about this and they say that this is an issue with GPUGRID application (https://github.com/BOINC/boinc/discussions/5894).

Where can I raise this issue to the project owners?

By checking the task manager when this happened earlier, I noticed that there were no "python" process, which should be the case for ATMML task.[/url]

Coincidently, I inadvertently suspended gpugrid and when I saw it, I resumed the project. I too saw that the previously active task was in limbo. It said running but it wasn't (fans were not running to confirm). I simply dished it and the waiting task took off like normal.