World Community Grid - View Thread - SIGSEGV: segmentation violation on BOINC for Android

World Community Grid Forums

Category: Support

Forum: Android Support Forum

Thread: SIGSEGV: segmentation violation on BOINC for Android

Quick Go »

No member browsing this thread

Thread Status: Active
Total posts in this thread: 15

[ ]

Author

This topic has been viewed 3188 times and has 14 replies

Cozmonaut
Cruncher
Joined: Aug 9, 2005
Post Count: 16
Status: Offline
Project Badges:

180 day badge for Human Proteome Folding

2 year badge for Human Proteome Folding - Phase 2

45 day badge for Nutritious Rice for the World

14 day badge for The Clean Energy Project

1 year badge for Help Fight Childhood Cancer

14 day badge for Influenza Antiviral Drug Search

45 day badge for Help Cure Muscular Dystrophy - Phase 2

2 year badge for The Clean Energy Project - Phase 2

180 day badge for Computing for Clean Water

180 day badge for Drug Search for Leishmaniasis

90 day badge for GO Fight Against Malaria

45 day badge for Computing for Sustainable Water

20 year badge for Mapping Cancer Markers

180 day badge for Uncovering Genome Mysteries

2 year badge for Outsmart Ebola Together

2 year badge for FightAIDS@Home - Phase 2

2 year badge for Microbiome Immunity Project

5 year badge for Africa Rainfall Project

5 year badge for OpenPandemics - COVID-19


SIGSEGV: segmentation violation on BOINC for Android

I initially posted this in the regular Support forum, but it looks like it has tuckered out. I'll try again here:

I installed the Andriod version of BOINC on my Samsung Galaxy S II Epic 4G Touch (Sprint), and several work units were processed while it was charging last night, but they all returned a status of Error in my Results Status page. I wasn't sure if I should post the problem here or in the FAH forum, but since I had one Beta work unit, I decided to post here.

Here's the message I'm getting:
Result Name: FAHV_ x3AO2_ IN_ FBP_ 0047740_ 0616_ 0--
<core_client_version>7.2.7</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[03:22:45] Number of tasks = 8
[03:22:45] Starting task 0,CPU time is 0.000000.
[03:22:46] ./ZINC11811511.pdbqt size = 25 6 ../../projects/www.worldcommunitygrid.org/fahv.x3AO2_IN_FBP.pdbqt size = 2554 0
[03:56:12] Finished task #-1048585 cpu time used 1081.610000
SIGSEGV: segmentation violation

Exiting...

</stderr_txt>
]]>

The message for the Beta work unit is very similar.

Is there anything I can check? Here's (some of) the Event Log:
The log is huge, so I stopped and restarted BOINC. When I emailed it to myself, this is what I got. I hope this is enough of the log:

Tue Jul 23 15:50:53 CDT 2013||Resuming network activity
Tue Jul 23 15:50:52 CDT 2013||(to change preferences, visit a project web site or select Preferences in the Manager)
Tue Jul 23 15:50:52 CDT 2013||suspend work if non-BOINC CPU load exceeds 50 %
Tue Jul 23 15:50:52 CDT 2013||don't use GPU while active
Tue Jul 23 15:50:52 CDT 2013||don't compute while active
Tue Jul 23 15:50:52 CDT 2013||max CPUs used: 1
Tue Jul 23 15:50:52 CDT 2013||max disk usage: 0.53GB
Tue Jul 23 15:50:52 CDT 2013||max memory usage when idle: 400.00MB
Tue Jul 23 15:50:52 CDT 2013||max memory usage when active: 400.00MB
Tue Jul 23 15:50:52 CDT 2013||Preferences:
Tue Jul 23 15:50:52 CDT 2013||Reading preferences override file
Tue Jul 23 15:50:52 CDT 2013||General prefs: using separate prefs for home
Tue Jul 23 15:50:52 CDT 2013|World Community Grid|Computer location: home
Tue Jul 23 15:50:52 CDT 2013|World Community Grid|General prefs: from World Community Grid (last modified 03-Sep-2011 12:49:31)
Tue Jul 23 15:50:32 CDT 2013||(to change preferences, visit a project web site or select Preferences in the Manager)
Tue Jul 23 15:50:32 CDT 2013||suspend work if non-BOINC CPU load exceeds 50 %
Tue Jul 23 15:50:32 CDT 2013||don't use GPU while active
Tue Jul 23 15:50:32 CDT 2013||don't compute while active
Tue Jul 23 15:50:32 CDT 2013||max CPUs used: 1
Tue Jul 23 15:50:32 CDT 2013||max disk usage: 0.53GB
Tue Jul 23 15:50:32 CDT 2013||max memory usage when idle: 400.00MB
Tue Jul 23 15:50:32 CDT 2013||max memory usage when active: 400.00MB
Tue Jul 23 15:50:32 CDT 2013||Preferences:
Tue Jul 23 15:50:32 CDT 2013||Reading preferences override file
Tue Jul 23 15:50:32 CDT 2013||General prefs: using separate prefs for home
Tue Jul 23 15:50:32 CDT 2013|World Community Grid|Computer location: home
Tue Jul 23 15:50:32 CDT 2013|World Community Grid|General prefs: from World Community Grid (last modified 03-Sep-2011 12:49:31)
Tue Jul 23 15:50:31 CDT 2013||Suspending network activity - GUI not active
Tue Jul 23 15:50:31 CDT 2013||Suspending computation - on batteries
Tue Jul 23 15:50:31 CDT 2013||Not using a proxy
Tue Jul 23 15:50:31 CDT 2013||(to change preferences, visit a project web site or select Preferences in the Manager)
Tue Jul 23 15:50:31 CDT 2013||suspend work if non-BOINC CPU load exceeds 50 %
Tue Jul 23 15:50:31 CDT 2013||don't use GPU while active
Tue Jul 23 15:50:31 CDT 2013||don't compute while active
Tue Jul 23 15:50:31 CDT 2013||max CPUs used: 1
Tue Jul 23 15:50:31 CDT 2013||max disk usage: 0.53GB
Tue Jul 23 15:50:31 CDT 2013||max memory usage when idle: 400.00MB
Tue Jul 23 15:50:31 CDT 2013||max memory usage when active: 400.00MB
Tue Jul 23 15:50:31 CDT 2013||Preferences:
Tue Jul 23 15:50:31 CDT 2013||Reading preferences override file
Tue Jul 23 15:50:31 CDT 2013||General prefs: using separate prefs for home
Tue Jul 23 15:50:31 CDT 2013|World Community Grid|Computer location: home
Tue Jul 23 15:50:31 CDT 2013|World Community Grid|General prefs: from World Community Grid (last modified 03-Sep-2011 12:49:31)
Tue Jul 23 15:50:31 CDT 2013|World Community Grid|URL http://www.worldcommunitygrid.org/; Computer ID 2421972; resource share 100
Tue Jul 23 15:50:31 CDT 2013||No usable GPUs found
Tue Jul 23 15:50:31 CDT 2013||Local time is UTC -5 hours
Tue Jul 23 15:50:31 CDT 2013||Disk: 1.97 GB total, 615.44 MB free
Tue Jul 23 15:50:31 CDT 2013||Memory: 800.00 MB physical, 0 bytes virtual
Tue Jul 23 15:50:31 CDT 2013||OS: Android: 3.0.31-1014481
Tue Jul 23 15:50:31 CDT 2013||Processor features: swp half thumb fastmult vfp edsp neon vfpv3 tls
Tue Jul 23 15:50:31 CDT 2013||Processor: 2 ARM ARMv7 Processor rev 1 (v7l)

Thanks,
Richard

[Jul 25, 2013 8:38:38 PM]

knreed
Former World Community Grid Tech
Joined: Nov 8, 2004
Post Count: 4504
Status: Offline
Project Badges:

90 day badge for Human Proteome Folding - Phase 2

90 day badge for Computing for Clean Water

14 day badge for Uncovering Genome Mysteries

45 day badge for Outsmart Ebola Together

180 day badge for FightAIDS@Home - Phase 2

1 year badge for Microbiome Immunity Project

1 year badge for Africa Rainfall Project

180 day badge for OpenPandemics - COVID-19


Re: SIGSEGV: segmentation violation on BOINC for Android

Can you go to the preferences tab, selected 'show advanced preferences and controls' and then find the setting 'CPU Limit'.

Please tell us what it is currently set at and then change it to 100%.

Let us know if you have better luck afterwords.

[Jul 26, 2013 2:13:03 AM]

Cozmonaut
Cruncher
Joined: Aug 9, 2005
Post Count: 16
Status: Offline
Project Badges:


Re: SIGSEGV: segmentation violation on BOINC for Android

Yesterday I uninstalled and reinstalled the app. Nothing changed.

I checked the "CPU Limit" setting and it's already at 100%. "Pause at CPU usage above" is 50%.

Thanks,
Richard

[Jul 26, 2013 5:03:00 PM]

knreed
Former World Community Grid Tech
Joined: Nov 8, 2004
Post Count: 4504
Status: Offline
Project Badges:


Re: SIGSEGV: segmentation violation on BOINC for Android

Ok - thank you for trying. We are investigating several issues and are currently testing an alpha version of the application. We hope to have a beta version to test soon.

[Jul 29, 2013 11:29:23 PM]

Cozmonaut
Cruncher
Joined: Aug 9, 2005
Post Count: 16
Status: Offline
Project Badges:


Re: SIGSEGV: segmentation violation on BOINC for Android

I wasn't aware that the BOINC for Android client was alpha code. Not that I mind, I just didn't know that. If there's any data that I can send to help diagnose the problem, just let me know.

Thanks,
Richard

[Jul 30, 2013 5:39:59 AM]

Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline


Re: SIGSEGV: segmentation violation on BOINC for Android

...I think he means there is a NEW one (alpha) under test to fix some of the issues... wink

[Jul 30, 2013 7:37:23 AM]

Cozmonaut
Cruncher
Joined: Aug 9, 2005
Post Count: 16
Status: Offline
Project Badges:


Re: SIGSEGV: segmentation violation on BOINC for Android

I see. I guess I could install the alpha code and see if it resolves the issue. Where would I get that?

To be honest, I was expecting someone to ask me to provide some additional information about the segmentation violation. Maybe a core file, or something. It would be a shame to release an update and not even have this issue resolved.

[Jul 31, 2013 6:06:23 PM]

knreed
Former World Community Grid Tech
Joined: Nov 8, 2004
Post Count: 4504
Status: Offline
Project Badges:


Re: SIGSEGV: segmentation violation on BOINC for Android

Our alpha testing environment is limited to just our test devices and machines. We have to get the code stable in that environment before we move it on to beta testing. Unfortunately, we continue to detect issues with the next revision in the alpha environment so we are continuing our investigation.

[Jul 31, 2013 10:35:12 PM]

Cozmonaut
Cruncher
Joined: Aug 9, 2005
Post Count: 16
Status: Offline
Project Badges:


Re: SIGSEGV: segmentation violation on BOINC for Android

Alrighty, I guess I'll just disable BOINC on my phone and wait for an update to be released to the Play store and hope the problem gets resolved.

Thanks,
Richard

[Aug 2, 2013 3:08:22 PM]