My 1.21 client 605860314_19_45810 task has been running for 100 minutes with no movement of the progress bar and has written the following into std_0 over 200 times:
Dephasing Warning: in a new state,now inverse the momentum and restart from step 0
Starting search for transition step with accuracy ...
Search found 3 matches
- Fri Dec 03, 2010 10:01 pm
- Forum: eOn
- Topic: Computation errors
- Replies: 41
- Views: 996633
- Wed Dec 01, 2010 6:25 pm
- Forum: eOn
- Topic: Incorrect calculation - Client 1.18
- Replies: 11
- Views: 311833
Re: Incorrect calculation - Client 1.18
I aborted 2 after an hour on each, and got 2 more.
I'll give them a few hours and see if they wake up.
I'll give them a few hours and see if they wake up.
segfaults
All the results on my Linux machine calculate and upload correctly but then the client exits with:
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<stderr_txt>
00:01:16 (2198): called boinc_finish
SIGSEGV: segmentation violation
Stack trace (2 frames):
[0x80a37a7]
[0xd6a400]
Exiting ...
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<stderr_txt>
00:01:16 (2198): called boinc_finish
SIGSEGV: segmentation violation
Stack trace (2 frames):
[0x80a37a7]
[0xd6a400]
Exiting ...