I've observed a possible anomaly a couple of times with 4.43 running on 9x. Just saw the post about 4.44 so I haven't done the upgrade yet.

Occaisionally when the scheduler does a project switch, and decides it need to go into ED mode, the elapsed CPU timer for the suspended project keeps incrementing even though there is apparently no CPU time being allocated as indicated with other process monitoring tools (I have it set to remain in memory).

I have not seen this happen when the scheduler makes the switch and remains in normal mode.

However, since I'm investigating BOINC's behaviour with machines on the low end of the horsepower spectrum, it may be a while before I get a chance to see if this happens on a regular basis.

Alinator

I've observed a possible anomaly a couple of times with 4.43 running on 9x. Just saw the post about 4.44 so I haven't done the upgrade yet.

Occaisionally when the scheduler does a project switch, and decides it need to go into ED mode, the elapsed CPU timer for the suspended project keeps incrementing even though there is apparently no CPU time being allocated as indicated with other process monitoring tools (I have it set to remain in memory).

I have not seen this happen when the scheduler makes the switch and remains in normal mode.

However, since I'm investigating BOINC's behaviour with machines on the low end of the horsepower spectrum, it may be a while before I get a chance to see if this happens on a regular basis.

Alinator

Is this the same as I have seen twice now?

I have seen a WU reported with 0% complete, but 9mins CPU in one case 17mins in another.

A reboot fixed this, and it seemed that both WUs hada actually done 15% to 40% work, just the percentage done had frozen ay zero.

---

I've observed a possible anomaly a couple of times with 4.43 running on 9x. Just saw the post about 4.44 so I haven't done the upgrade yet.

Occaisionally when the scheduler does a project switch, and decides it need to go into ED mode, the elapsed CPU timer for the suspended project keeps incrementing even though there is apparently no CPU time being allocated as indicated with other process monitoring tools (I have it set to remain in memory).

I have not seen this happen when the scheduler makes the switch and remains in normal mode.

However, since I'm investigating BOINC's behaviour with machines on the low end of the horsepower spectrum, it may be a while before I get a chance to see if this happens on a regular basis.

Alinator

DO NOT USE "remain in memory" with Win9x OS (possibly ME also). This is a well known issue which has never been addressed by the dev.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

I've observed a possible anomaly a couple of times with 4.43 running on 9x. Just saw the post about 4.44 so I haven't done the upgrade yet.

Occaisionally when the scheduler does a project switch, and decides it need to go into ED mode, the elapsed CPU timer for the suspended project keeps incrementing even though there is apparently no CPU time being allocated as indicated with other process monitoring tools (I have it set to remain in memory).

I have not seen this happen when the scheduler makes the switch and remains in normal mode.

However, since I'm investigating BOINC's behaviour with machines on the low end of the horsepower spectrum, it may be a while before I get a chance to see if this happens on a regular basis.

Alinator

DO NOT USE "remain in memory" with Win9x OS (possibly ME also). This is a well known issue which has never been addressed by the dev.

Thanks for the heads up on the known issue, although I neglected to log what memeory mode I was running in the first time I saw it (think it was in the default remove mode, but am not sure though).

Interestingly, I cleared the anomaly by exiting BOINC and then restarting it.

The anomaly happened on the first switch after attaching to the second project on the two machines where I've observed it happen. However since then, it has made several mode switches and the behaviour has not repeated.

Alinator