TYT, CP.

Let's see if I can summarize all the issues, OTOH:

1) Output file too large (Error -131)
2) Maximum Disk Use Exceeded (disk_bound overstepped)
3) Memory model exceeded (memory_bound overstepped)
4) Loss of -large- portions of CPU time at time of reporting, which looks to happen at end.
5) Progress % erratic (e.g. happens it can from 0.5% to 50% only at end of 1st pass when there are only 2 passes)
6) Related to 5), checkpoints at times multiple hours apart... not good for part time crunchers.
7) Jobs seem stuck in memory at times, [when seemingly no more progress is made]... wont unload, even when "Leave application in memory when suspended" is off. Full client restart required to get them to unload.
8) Some tasks freeze on the CPU time use when running [is it the display or is it the CPU time in Task Manager indicates no CPU time use?], while elapsed time keeps accumulating and progress % goes backward. Users of BOINC manager wont see this easily, to users of BOINCTasks it's obvious since both Elapsed and CPU time is shown.

Wish list: Printing of OS and CPU details in Result Log.

Did I miss any? (Copy list and insert 9) and so on.

The DIY department.

P.S. Whilst the 10,000 originals left the feeder in 1.5 hours and were sent quite early in the day, 'only' 3,556 had validated at midnight [Don't know but doubt the 'error' results that were credited were included... my own count, 9 shown at midnight as valid on My Grid, but 18 listed with credit, including 9 with error. 2 in PV].

Well, that one that was running overnight finally finished, and just before I could take a look at it. The server logs show:

BETA_ BETA_ 9999987_ 0168_ 0-- <M/c-ID> Pending Validation 31/10/13 06:55:37 01/11/13 10:10:15 12.33 / 24.69 235.2 / 0.0

It clearly finished without recording any CPU time for the second half of the run, but at least it finished. I have no idea whether or not it checkpointed again, but I suspect not. One checkpoint near the beginning and then 24 hours running without one is clearly not a good idea ...

So far, all the others I've had were resends that all failed (again) with oversize output files.

Here's wishing the techs a successful time tracking down these and the other issues that people have seen.

That sounds very much like the issue I'm getting on my Windows 7 64-bit machine at home, but I didn't get chance to inspect the detailed logs.

SekeRob, from your excellent summary of issues, I think one may have been missed one off (as to whether it's a concern or not, I don't have enough data - it may just be my machine/set-up, or it may be more widespread). Anyhow, as you requested, I'll copy your list of 8 and add a 9th onto the end;

1) Output file too large (Error -131)
2) Maximum Disk Use Exceeded (disk_bound overstepped)
3) Memory model exceeded (memory_bound overstepped)
4) Loss of -large- portions of CPU time at time of reporting, which looks to happen at end.
5) Progress % erratic (e.g. happens it can from 0.5% to 50% only at end of 1st pass when there are only 2 passes)
6) Related to 5), checkpoints at times multiple hours apart... not good for part time crunchers.
7) Jobs seem stuck in memory at times, [when seemingly no more progress is made]... wont unload, even when "Leave application in memory when suspended" is off. Full client restart required to get them to unload.
8) Some tasks freeze on the CPU time use when running [is it the display or is it the CPU time in Task Manager indicates no CPU time use?], while elapsed time keeps accumulating and progress % goes backward. Users of BOINC manager wont see this easily, to users of BOINCTasks it's obvious since both Elapsed and CPU time is shown.
9) Running 4 concurrently (i.e., using all available cores), appears to be very inefficient.

It happened again. File size to big. Well, I'm two for two. Batting 1000.