| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Android Support Forum
Thread: Tasks returning with error |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
amejr999
Cruncher Joined: Feb 17, 2011 Post Count: 1 Status: Offline Project Badges: 
|
Hi all,
I am running an Android Nexus 7 (2013) running Android 6.0.1 and BOINC 7.4.41. Recently all of my projects have been delivering errors. Below is the result log for one project: Result Name: OET1_ 0001566_ xEBGP-F_ rig_ 33357_ 1-- <core_client_version>7.4.41</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> stackdumps unavailable INFO: No state to restore. Start from the beginning. [07:39:53] Number of tasks = 1 [07:39:53] Running task 0,CPU time at start of task 0 was 0.000000 [07:39:53] ./ZINC09366347.pdbqt size = 30 6 ../../projects/www.worldcommunitygrid.org/oet1.xEBGP-F_rig.pdbqt size = 2443 0 SIGSEGV: segmentation violation Exiting... </stderr_txt> ]]> My tablet is getting Outsmart Ebola tasks, and it seems to be erroring consistently. Any help would be appreciated. Thanks. |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Actually with the advent to Marshmallow my Nexus 7(2013) moved to practically zero errors on OET1, though yesterday had the first [a 193] since start of Android 6 install, beginning November. Even moved from allowing 3 cores crunching instead of 2.
----------------------------------------If I see error I do a power cycle and usually all is good again. Make sure there's enough space and what I do is swipe off any apps lingering in memory such as Firefox [which is I'm told a bad habit]. Notwithstanding, keep doing this to prevent low-memory alerts. [Edit 1 times, last edit by SekeRob* at Dec 14, 2015 9:16:34 AM] |
||
|
|
|