Just to give everyone a status. The following issues have been identified and the fix applied:

• Some workunits contain invalid data and prevent the application from launching. We have suspended these workunits.
  
• The file size for results was specified too small for some computers. It has been increased by a factor of 4.

The following issues are being investigated now:

• Some workunits have revealed a memory leak that can cause the application to use up to 256MB of RAM. We are temporarily increasing the min RAM required for the project until this is fixed
  
• Certain workunits experiencing errors because they are having troubles opening the checkpoint file
  
• There are a couple of additional items that we are also investigating.
  

We will continue to send out work for the project as we received over 2000 results successfully so far.

I have 36 RICE tasks queued that all have the 1.5MB filesize limit. Instead of aborting all of them, is it possible to edit the client_state file and change the limit myself? Here is some data for an output file:

<name>R00000_0f42cd9f696c7cb7d97196270bebc6f7_06_17_0</name>
<nbytes>0.000000</nbytes>
<max_nbytes>1500000.000000</max_nbytes>
<generated_locally/>
<status>0</status>
<upload_when_present/>
<gzip_when_done/>
<url>https://secure.worldcommunitygrid.org/boinc/w...pload_handler</url>
<signed_xml>
<name>R00000_0f42cd9f696c7cb7d97196270bebc6f7_06_17_0</name>
<generated_locally/>
<upload_when_present/>
<max_nbytes>1500000</max_nbytes>
<url>https://secure.worldcommunitygrid.org/boinc/w...pload_handler</url>
<gzip_when_done/>
</signed_xml>

If I change the two <max_nbytes> entries to 6000000, will that allow the output files to exceed 1.5MB? Since I have a Q6600 running at 3.2GHz, I am anticipating some of the files going over the 1.5MB limit.

We believe that we have fixed the memory lead and one of the major additional errors. We will be starting a beta test within 45 minutes. This is going to be a fast beta test with 6 hour deadlines (workunits will take 1 hour).

Once this version is released, along with the corrected file size limits, we expect to see 65% fewer errors. Additionally, fixing these problems will reduce the amount of cpu time lost due to errors by 95%.

Send them on. I have the Beta project checked in my profiles. I'm running Core 2 Quads with minimum of 2GB RAM in every machine and I have a variety of operating systems: 32 bit XP Pro, 32 bit Vista Ultimate, 32 bit Vista Business, 64 bith Vista Ultimate, 64 bit Server 2008...... If there's still a problem with faster machines I should see it. I'll also throw a 3.4GHz P4 Northwood with XP Home on here just to see what happens with it.

Just to report something I noticed:

I'm not seeing any error messages other than
Task R00001_<whatever> exited with zero status but no 'finished' file
If this happens repeatedly you may need to reset the project.

However I'm running this app on 4 hosts and only one of them gets this error -- and it gets it every time. The result output looks OK, except for the can't open pdb for appending message; they're all currently are in pending status.

The host with these messages is a Mac(book Pro), the other 3 are Windows. Also it's a dual core, the others are H/T P4 or less. My prefs limit BONC to 1 cpu.

I can do what it suggests and reset the project on this host, but I'm a bit skeptical that will make a difference.