6.10.43/44 have apparently been withdrawn due to a problem with GPU process.

The withdrawal was posted in BOINC News, but not here.

Since the release of 6.10.43/44 was also announced here, its withdrawal needs also to be posted here.

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

I had posted about it in the 6.10 change log thread. Have now edited it into the first post of both the 6.10.43/.44 threads.

---

I asked for an explanation on why we went back to .18, which doesn't have any prevention code whatsoever in place. Rom answered me:

Rom Walton wrote:

The previous behavior, what is in .18, is that the task instance just crashes, the project should then reduce the quota for the machine. The situation would eventually resolve itself so that the host was only getting one or two task instances a day.

From .25 through to .45, the host would just keep requesting new work without even attempting to launch the existing task instances. Eventually the HD would become full, if the preferences didn't prevent it. On one host 2000+ task instances were downloaded.

---

6.10.43/44 have apparently been withdrawn due to a problem with GPU process.

The withdrawal was posted in BOINC News, but not here.

Since the release of 6.10.43/44 was also announced here, its withdrawal needs also to be posted here.

So is it fair to say that v6.10.43 is still safe to run with no GPU processing enabled? The project I'm running (WCG) uses no GPU processing anyway, so I don't think going back to v.6.10.18 would be of any real use/benefit/advantage to me.

Unless you happen upon the problem with the GPU having not enough memory and BOINC downloading more work for it anyway, you can easily continue running 6.10.43/.44

---