Android apps often die due to being killed by the OS or due to run time
memory allocation failures (i.e. standard lazy allocations that can't be
fulfilled when a page is needed, including stack pages.)

That said, I haven't noticed it being a problem.  It seems that the android
version allows a lot of restarts......
http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=15399861


On Tue, Mar 18, 2014 at 12:09 PM, David Anderson <[email protected]>wrote:

> Are any other computers having this problem?
> Let's maintain some perspective.
>
> TOO_MANY_EXITS is not caused by BOINC suspending/resuming the app.
> On Windows, it typically means that something outside BOINC is killing the
> app.
> Perhaps security software; BOINC has no way of knowing.
> Problems like this are usually solved by communicating with the volunteer.
>
> I'm not sure what you mean by "black box".
> BOINC is the opposite of a black box.
> Do you have any specific suggestions?
>
>
> On 18-Mar-2014 8:05 AM, Richard Haselgrove wrote:
>
>> Looking around at SETI, trying to analyse how well the server was
>> performing
>> while the status page was dysfunctional, I came across this user.
>>
>> http://setiathome.berkeley.edu/show_host_detail.php?hostid=7220378
>>
>>
>> He (and his - somewhat elderly - computer) have been members for about 3
>> weeks.
>> He's got a little credit, both at SETI and at Cosmology, so the computer
>> seems to
>> be in working order.
>>
>> But now, every single task - at both projects, today - is failing with
>> Exit
>> status-226 (0xffffffffffffff1e) ERR_TOO_MANY_EXITS (oh, and a few download
>> errors).
>>
>> He seems to be using what was the recommended BOINC at the time
>> (v7.2.39), stock
>> science applications, and I'd be willing to bet default BOINC computing
>> settings.
>> BOINC has just *got* to work for volunteers like that, out of the box -
>> otherwise
>> there's no point.
>>
>> So, as a reasonably experienced "reader of the runes", what can I deduce
>> from the
>> error messages presented that I might possibly pass on in a helpful
>> private
>> message? Er, as it happens, nothing. I'm stuck. Even task
>> http://www.cosmologyathome.org/result.php?resultid=28640358 - which ran
>> for
>> nearly two hours - presents nothing useful in stderr_txt.
>>
>> If we're going to seal the black box, so that no information leaks out to
>> the
>> target "volunteer spare cycles" user, then the onus is on us to make sure
>> it
>> works. First time, every time.
>>
>> Otherwise it's no surprise the number of volunteers goes down, year after
>> year.
>> _______________________________________________ boinc_dev mailing list
>> [email protected]
>> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe,
>> visit
>> the above URL and (near bottom of page) enter your email address.
>>
>>  _______________________________________________
> boinc_dev mailing list
> [email protected]
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to