Thanks for reporting errors!

---

Work Unit https://ralph.bakerlab.org/result.php?resultid=578249

CPU time 47889.688918
<core_client_version>5.9.4</core_client_version>
process exited with code 1 (0x1)

<stderr_txt>
d cos value legal range
sin_cos_range ERROR: nan is outside of [-1,+1] sin and cos value legal range
...
sin_cos_range ERROR: nan is outside of [-1,+1] sin and cos value legal range
ERROR:: Exit from: refold.cc line: 338
</stderr_txt>

This thread needs sticky.
Older threads need to de-sticky.

---

I have alot of - exit code -1073741819 (0xc0000005)
with this kind of wu-s

Anders n

---

I have alot of - exit code -1073741819 (0xc0000005)
with this kind of wu-s

Anders n

Problems confirmed with this series of wus on Mac:

2ffm_1_NMRREF_1_1pqx_1_idid_model_04IGNORE_THE_REST_idl_2218_10_0


2ffm_3_NMRREF_3_1pqx_1_idid_model_01IGNORE_THE_REST_idl_2218_10_0

Crashed after 6-8 min., could not complete model 1 step 0, thread 2 crashing.

Exit status
-177 (0xffffffffffffff4f)

<message>
Maximum disk usage exceeded
</message>
[[Boinc is allowed 20 Gb disk space]]

Problems with this series of wus on Linux:
2ffm_1_NMRREF_1_1pqx_1_idid_model_08IGNORE_THE_REST_idl_2218_4_2
2ffm_3_NMRREF_3_1pqx_1_idid_model_02IGNORE_THE_REST_idl_2218_7_2
2ffm_2_NMRREF_2_1pqx_1_idid_model_04IGNORE_THE_REST_idl_2218_10_1

CPU time 14.600912
<core_client_version>5.9.4</core_client_version>
process exited with code 193 (0xc1)

SIGSEGV: segmentation violation
Stack trace (20 frames):
[0x8cf297b]
...

https://ralph.bakerlab.org/result.php?resultid=584533]

core_client_version>5.10.7</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# cpu_run_time_pref: 7200
# random seed: 2388521


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x004D548A read attempt to address 0x07362000

Engaging BOINC Windows Runtime Debugger...
********************

---

These all failed the same way:

2ffm_2_NMRREF_2_1pqx_1_idid_model_01IGNORE_THE_REST_idl_2218_1_2
2ffm_1_NMRREF_1_1pqx_1_idid_model_07IGNORE_THE_REST_idl_2218_1_1
2ffm_4_NMRREF_4_1pqx_1_idid_model_04IGNORE_THE_REST_idl_2218_5_2
2ffm_5_NMRREF_5_1pqx_1_idid_model_02IGNORE_THE_REST_idl_2218_6_1
2ffm_2_NMRREF_2_1pqx_1_idid_model_08IGNORE_THE_REST_idl_2218_6_1

<core_client_version>5.10.7</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# cpu_run_time_pref: 3600
# random seed: 2388882


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x004D548A read attempt to address 0x07DB2000

(different random seed on them all, but the exit code and addresses are the same)

Lots of problems with the '2ffm' work units,
All fail after 10 to 20 seconds, as posted by others in above posts.
Had 12 fail.
Wont put links in as already some above, all mine are Access Violations.

WU numbers are 584610, 584477, 584408, 584406, 584398, 584386, 584382, 583681, 583679, 583205, 583199, 583094.

---

Hello

I've a work unit, https://ralph.bakerlab.org/workunit.php?wuid=517057, that crunch since 53 hours 9 mn.

it's normal ? Can I abort then ?

thank

Laurent

---

Hello

I've a work unit, https://ralph.bakerlab.org/workunit.php?wuid=517057, that crunch since 53 hours 9 mn.

it's normal ? Can I abort then ?

thank

Laurent

Not normal. Maximum time in Rosetta that you can set in your prefances is 24 hours. Default is about 3 hours (I think). the only time that Rosetta disregards the prefance time is when it is trying to complete a Decoy (usually the first one).
I think you can abort that one. Appears stuck.

---

> Still failing on all '2ffm' type workunits in less than 10 seconds with Segmentation Violations.
585333
585332

---

Just aborted two workunits with 14 hours plus apiece. These same two workunits were restarted when I recycled BOINC Manager with 24+ hours on one and over 40 hours on the other. At the time, they were at 100% completion and recycled back to the beginning upon restart. They are:

Work Unit #1
and
Work Unit #2

---

Add the following two workunits to the list of aborted workunits. Each significantly missed their target times and showed that they were in the INITIALIZING stage with 100% completion.

2ffm_1_NMRREF_1_1pqx_1_idid_model_06IGNORE_THE_REST_idl_2218_1

and

2ffm_1_NMRREF_1_1pqx_1_idid_model_04IGNORE_THE_REST_idl_2218_9

---

I just got this 2acy__BOINC_ABINITIO_BARCODE-2acy_-frags83__2230_424_0 WU and it is running in 65MB of memory!! That's HALF normal. I'm on model 63 now and peak memory for the Windows task is 64MB.

Have you been working to reduce memory footprint? Or is it just an "easy" WU?

---

When displaying the graphic and pressing "B" three times to display the view with the balls, if you rotate the image 180 degrees to the left, you end up displaying the shaded portion of the sun effect. Seems the orientation of the sun should probably be fixed relative to the viewer of the graphic, so all the windows would always show the sun in the upper right, even if you rotate one of the images.

Also, currently running a Rosetta 5.68 jumping task and the image in the searching and accepted boxes is bouncing all around. i.e. it is not properly centered in the box. However, changing the view back to the ribbons and it is centered normally. Looks like the low energy box is effected the same way.

---

Sorry about this -- the shaded sphere view is experimental. Glad to hear that the ribbons view still works fine.

When displaying the graphic and pressing "B" three times to display the view with the balls, if you rotate the image 180 degrees to the left, you end up displaying the shaded portion of the sun effect. Seems the orientation of the sun should probably be fixed relative to the viewer of the graphic, so all the windows would always show the sun in the upper right, even if you rotate one of the images.

Also, currently running a Rosetta 5.68 jumping task and the image in the searching and accepted boxes is bouncing all around. i.e. it is not properly centered in the box. However, changing the view back to the ribbons and it is centered normally. Looks like the low energy box is effected the same way.

---