I saw this wu...

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=1559573628

on my system. Normally, the jobs here run to completion in 5-6 minutes, but this one was 56% complete, not increasing, and had over a day of crunching time logged. I suspended and released it, the percentage done dropped and it started again running to completion quickly. You can see by the sent/returned dates that something weird happened. I've not noticed this before here, but it has certainly worried me, as I have the project on here, a system I do not look at much, it is simply a number cruncher.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream...

I have this problem too.
Stopping and restarting
Boinc client clears the time to 5-6 minutes again.

First, the link posted does not seem to work?

I had a similar problem for Seti WUs that used Intel GPUs. Work would start, but ETA would never end. If you paused crunching on the WU, it would just restart. I discovered that thrashing was an overall problem with iGPUs, so I just stopped using the processor on BOINC.

This problem sprouted all of a sudden one day; I don't think I had any changes on my system so I suspect it was something with the WU itself.

Sorry, I know that doesn't help.

>>> First, the link posted does not seem to work?

It does not work anymore, it did when I posted it.

Because the database clears results from the BOINC server after so many days else you'd start to get huge performance degradation.

Typically, the more active a project, the shorter the period. The alternative is investing in really expensive corporate enterprise servers...

I saw this wu...

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=1559573628

on my system. Normally, the jobs here run to completion in 5-6 minutes, but this one was 56% complete, not increasing, and had over a day of crunching time logged. I suspended and released it, the percentage done dropped and it started again running to completion quickly.

Seen that a number of times. I think it's an ongoing bug they are battling. If you don't want to babysit, turn N-body off. Pretty annoying to come home and realize your computer been spinning its wheels on a WU since last night...

A bit of a kick to this topic, but apparently I am running into the same issue with N-body tasks.

Once my display turn off (power saving option) the task basically stops running, timer moves on, task calculations don't.

After returning, it shows the following:
https://tweakers.net/ext/f/ulINereZ3BO5WoqV9aqqHxlB/full.png

After restarting BOINC, this:
https://tweakers.net/ext/f/iqFyPTv2veSk6YY07Rwg5hxS/full.png

For now it only happened with N-body tasks during my project testing period.
If this doesn't occur the WU also finishes within 10 minutes, unlike the 20ish it needed for that after it occurred.

Been trying a lot, drivers updated, latest version of BOINC, no other programs running, keeping the machine active.

But doesn't matter if I keep the machine active or not, eventually the {mt} task will stop running. As it is now I will just remove {mt} WU's and turn them off. Shame I have to, but they keep suspending progression.

Been trying a lot, drivers updated, latest version of BOINC, no other programs running, keeping the machine active.

But doesn't matter if I keep the machine active or not, eventually the {mt} task will stop running. As it is now I will just remove {mt} WU's and turn them off. Shame I have to, but they keep suspending progression.

Alot of us are in the same boat, they just won't work like they should all the time so we've moved on. As long as it does work for enough people they will keep sending them out.

I haven't seen a long running work unit yet, but I am on Ubuntu 16.04 (i7-4770). It might be a Windows problem?
https://milkyway.cs.rpi.edu/milkyway/results.php?hostid=763264