boun...@ssl.berkeley.edu>]
On Behalf Of Robert Miles
Sent: Tuesday, March 7, 2017 8:22 AM
To: boinc_dev@ssl.berkeley.edu<mailto:boinc_dev@ssl.berkeley.edu>
Subject: Re: [boinc_dev] boinc_dev Digest, Vol 153, Issue 3
From what I've seen, when BOINC suspends workunits, this DOES NOT fre
s
> Sent: Tuesday, March 7, 2017 8:22 AM
> To: boinc_dev@ssl.berkeley.edu
> Subject: Re: [boinc_dev] boinc_dev Digest, Vol 153, Issue 3
>
> From what I've seen, when BOINC suspends workunits, this DOES NOT free the
> memory they are using.
>
> It looks like BOINC should not be allo
Digest, Vol 153, Issue 3
From what I've seen, when BOINC suspends workunits, this DOES NOT free the
memory they are using.
It looks like BOINC should not be allowed to start a workunit without
checking
whether enough memory is still free, and it should then be required to
repeat
this check
From what I've seen, when BOINC suspends workunits, this DOES NOT free the
memory they are using.
It looks like BOINC should not be allowed to start a workunit without
checking
whether enough memory is still free, and it should then be required to
repeat
this check before starting the next
