On my xp 64 box, host #581, all these units err out after around 1m15. Anyone else?
Aborted the few left in cache, but can't keep an eye on it 16x7.

The 2m941 work units use much more memory, about 1 GB per task, than the others. BOINC should not be starting them if there is not sufficient memory for them, but it seems to be in some cases anyway. You can disable them entirely by deselecting lasievef in NFS@Home preferences in your account.

It errors out in my machine as well. With the below error message. Is it the same case? I had done lasievef work units previously in the same machine. Had few troubles earlier also though.

<core_client_version>6.2.28</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
boinc initialized
work files resolved, now working
-> projects/escatter11.fullerton.edu_nfs/lasievef_1.07_windows_intelx86.exe
-> -r
-> -f
-> 205106000
-> -c
-> 1000
-> -R
-> ../../projects/escatter11.fullerton.edu_nfs/S2m941.poly
-> -o
-> ../../projects/escatter11.fullerton.edu_nfs/S2m941_205106_r_0_0
xmalloc: m
called boinc_finish

</stderr_txt>
]]>

Yes, xmalloc errors indicate that there was not enough contiguous memory available for the workunit. These 2m941 workunits use much more memory than the R269 workunits. It's fine to just allow them to error out or to manually abort them as they get automatically reissued. But if you wish, you can disable lasievef until these clear. I'll post a notice in this thread when they're gone.

I'll post a notice in this thread when they're gone.

All but a handful of 2m941 workunits have now been completed, so it is unlikely that you will see any more of them. If you have disabled lasievef in your NFS@Home preferences due to these high-memory workunits, then you can now enable it again. We are now working on 10,268+, which uses about 500 MB per workunit.