I am seeing tasks using almost 6 gb of RAM each. Is that intentional? Most machines will choke on that.
____________
Reno, NV
Team: SETI.USA

Am seeing the same, ouch

Should we abort any tasks already in progress? Or let them complete?
____________
Reno, NV
Team: SETI.USA

I stopped new tasks, will finish the ones I have.
Hope we get some news on what is happening.

I aborted all mine. It kept crashing my computers.

I can't abort just yet as I can't get back into my computer due to it not responding anymore. Lack of memory for such tasks. 6 cores and only 8 MB, with a few WUs using over 4GB each, has just about killed my computer.

Conan

In a PC with 32 GB RAM those large WUs finish properly in approx. 5 hours. They were credited 700 - 1000 points.

I'm sorry but I'll have to abort my tasks and wait for the memory issue to get solved first.
Most my computers haven't got more than 1 Gb/core,
so I cannot crunch anything that takes more than 750 Mb/task!
(Except for some of the heaviest Rosetta tasks I haven't seen anything else yet
that have stopped my computers due to excessive memory requirements.)
I think 6Gb/task will be a showstopper for most crunchers, so I hope the issue can be solved soon!
//Gunnar

Seems to be a garbage collection issue.
I have 32GB of RAM, and 32 threads, and regularly see 10 threads or more waiting for memory.
When I restart the service, it loads all the WUs from before, plus the remaining empty cores, and still has about 50% of memory spare.
If you look into HTOP, it shows in the memory bar as a brown color (cache), and could easily be moved to swp.

For those who are using Linux, you'll be able to limit the amount of threads allocated to mindmodeling at a time, by being root, and creating or modifying the file
/var/lib/boinc/projects/mindmodeling.org/app_config.xml

In Windows, I presume the file to be in:
C:\ProgramData\BOINC\Projects\mindmodelling.org
But I'm not running windows, so I could be wrong.

<app_config>
<app>
<name>ccl_wrap_linOnly</name>
<max_concurrent>6</max_concurrent>
</app>
</app_config>

I am seeing tasks using almost 6 gb of RAM each. Is that intentional? Most machines will choke on that.

Ram usage of this task is huge.

I had run one WU run for slightly over 2 hours. Task seems to stuck at 9% so I suspended all work and re-enabled it straight away. WU finished within 7 seconds and reported as valid. CPU runtime was zero.

Exactly same problem as mine was reported already

Apologies. There was an issue with how the job was setup, which resulted in many computational errors. The job was suspended while we fix the problems.

Bummer. I was content to be helping out here. And I'd be happy enough to keep running that batch, seeing as so far I'd only logged two Error'ed units.

Oh well. Hopefully there's other work on its' way.

Apologies. There was an issue with how the job was setup, which resulted in many computational errors. The job was suspended while we fix the problems.

I see we have new tasks to crunch, and they are still requiring up to 6gb per task. Insanity. I thought this was going to be fixed?

One of our scientists is trying to submit a job with a couple of problems. We have decided to move his task to a resource with higher computing power. Unfortunately, this will probably mean that volunteers will not have a job to crunch on.

Apologies. There was an issue with how the job was setup, which resulted in many computational errors. The job was suspended while we fix the problems.

I see we have new tasks to crunch, and they are still requiring up to 6gb per task. Insanity. I thought this was going to be fixed?

One of our scientists is trying to submit a job with a couple of problems. We have decided to move his task to a resource with higher computing power. Unfortunately, this will probably mean that volunteers will not have a job to crunch on.

Would not be easier to change project settings to stop feeding WUs to users with not enough RAM?