I reset the project and dl 3 w/u. All failed with
<core_client_version>7.16.3</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
SIGSEGV: segmentation violation
Stack trace (8 frames):
../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse3(boinc_catch_signal+0x47)[0x422c97]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x15540)[0x7ffb3b1aa540]
../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse3[0x40ac20]
../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse3[0x4078b1]
../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse3[0x407467]
../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse3[0x40e591]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7ffb3afcb1e3]
../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse3[0x4057a1]

Exiting...

</stderr_txt>
]]>

This is with ubuntu 19.10
It did manage 1 w/u to completion befor I reset the project

Hi nairb,

Thank you for contributing Asteroids@home.

Recently we've being receiving some amount of misaligned input data from our feed which led to this issue as in your case. Some times our routines can't handle well misaligned data and as a result that could directly affect Work Units. Still it is taken into account so no data has been lost.

Please be patient as our team is constantly working to improve the code base, data handling and pre- and post-process routines.

Thanks.
Georgi

A few more w/u failed but seems to be working good again on linux & windoze10

Panic over .......

My raspberry 3B+ and Zeros that running stretch are getting constant computation errors. The raspberry 4's that are running buster are processing units properly. They have the latest boinc app installed. Please advise

I would ditch the Zero's, as they are using an ARM11 CPU (ARMv6 instruction set), and install Buster on the RPI3's too.

---