I upgraded to 6.6.20 on my WinXP x64 box and since then the SETI application seems to stay 'running' even after the WU has completed or paused I've paused computation (for pause I have it so the apps do not stay memory resident). What I mean by running is that the application is visible in Task Manager but does not take any CPU/GPU resources. However, when that happens new SETI CUDA WU's are starting but make no progress on computation. Suspending the SETI project results in 2 apps remaining in memory and my other CUDA project (GPUGrid) taking up both of my GPU's. If I resume SETI, then a 3rd SETI process will start up, etc. Have no problems with the GPUGrid WU's. Only way to get SETI WU's to start up again is to exit BOINC or manually kill the processes.

Specs of the box are WinXP x64, 8gig memory, 2x 9600 GT in non-SLI.

Any ideas why this is happening? Let me know if you want more details or need me to turn on some debugging goodies.

Thanks,

Jim

---

Bueller?

Anyone have a clue why this is happening?

Thanks,

Jim

---

Sounds to me like a scheduling bug that has been talked about a few times.
Boinc runs CUDA in EDF (earliest deadline first) mode all the time.
I'd bet that when boinc paused the tasks the seti units most likely didn't reach a checkpoint so they stay in memory until they run again.
When resumed however boinc started new wu's.

So I'd say nothing to worry about... unless you need the ram?

~Bob

---

Do you Good Search for Seti@Home? http://www.goodsearch.com/?charityid=888957
Or Good Shop? http://www.goodshop.com/?charityid=888957

Nope don't need the RAM at all. Just kinda sucks that BOINC can get in to a state where it thinks there are 2 GPU tasks running when in fact there are none.

Jim

---