Please post problems with Rosetta@home 5.43 here. We're especially interested in whether graphics-related crashes are reduced with this version. In January, we'll be trying updates with some of the graphics features revived, and with some new modes of Rosetta. So your feedback over the next few weeks is important to us, if you can spare the time!

---

What no problems yet ?

---

Team mauisun.org

Yes, I clicked and dragged on the graphics screen and it instantly crashed. The affected job was stopped and listed as a computation error in the client.

I've never tried clicking and dragging before on previous versions - wasn't aware that mouse rotation was possible. So I can't say whether this might have worked for me in previous versions. But it's certainly broken in 5.43.

---

Whoa, that's a bummer. Amazing, Philip, your computer has a perfect success rate previous to this crash! If you see further crashes (without clicking/dragging), please let us know.

Its going to take a couple days before the 5.43 WUs really become widespread; many users probably are going through their cache of 5.41 WUs still. We're crossing our fingers ... things looked very good on ralph. [There was a posting there of a computer that also crashed when two graphics windows were opened, on a multicore machine; I wonder if the problem is just with the "show graphics" window.]

Yes, I clicked and dragged on the graphics screen and it instantly crashed. The affected job was stopped and listed as a computation error in the client.

I've never tried clicking and dragging before on previous versions - wasn't aware that mouse rotation was possible. So I can't say whether this might have worked for me in previous versions. But it's certainly broken in 5.43.

---

Just installed 5.43 and tried dragging the graphics screen all around, unable to reproduce this problem. Can drag it all over my screen and enlarge and shrink to any size and it keeps on chugging away.

Whoa, that's a bummer. Amazing, Philip, your computer has a perfect success rate previous to this crash! If you see further crashes (without clicking/dragging), please let us know.

Its going to take a couple days before the 5.43 WUs really become widespread; many users probably are going through their cache of 5.41 WUs still. We're crossing our fingers ... things looked very good on ralph. [There was a posting there of a computer that also crashed when two graphics windows were opened, on a multicore machine; I wonder if the problem is just with the "show graphics" window.]

Yes, I clicked and dragged on the graphics screen and it instantly crashed. The affected job was stopped and listed as a computation error in the client.

I've never tried clicking and dragging before on previous versions - wasn't aware that mouse rotation was possible. So I can't say whether this might have worked for me in previous versions. But it's certainly broken in 5.43.

---

Just had to detach from the project, tried to reschedule but no luck.

3 of the last 5 WU's froze apparently due to graphics, now the project is telling me I do not have enough space for new WU's

Attached is list of messages received to see if this is of any assistance to developers.

15/12/2006 09:18:46|rosetta@home|Resuming task s018__BOINC_LOOP_RELAX_IGNORE_THE_REST_hom001__IGNORE_THE_REST_mapback_hom009_S_00002_0004955_0_1446_133_0 using rosetta version 543
15/12/2006 12:02:29|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
15/12/2006 12:02:29|rosetta@home|Reason: To fetch work
15/12/2006 12:02:29|rosetta@home|Requesting 3150 seconds of new work
15/12/2006 12:02:33|rosetta@home|Scheduler request succeeded
15/12/2006 12:02:33|rosetta@home|Message from server: No work sent
15/12/2006 12:02:33|rosetta@home|Message from server: (there was work but you don't have enough disk space allocated)
15/12/2006 12:02:33|rosetta@home|Message from server: BOINC will delete file jump_templates_v2.dat.gz when no longer needed
15/12/2006 12:02:33|rosetta@home|Got server request to delete file jump_templates_v2.dat.gz
15/12/2006 12:02:33|rosetta@home|No work from project
15/12/2006 13:59:15||Rescheduling CPU: application exited
15/12/2006 13:59:15|rosetta@home|Computation for task s018__BOINC_LOOP_RELAX_IGNORE_THE_REST_hom001__IGNORE_THE_REST_mapback_hom009_S_00002_0004955_0_1446_133_0 finished
15/12/2006 13:59:17|rosetta@home|Started upload of file s018__BOINC_LOOP_RELAX_IGNORE_THE_REST_hom001__IGNORE_THE_REST_mapback_hom009_S_00002_0004955_0_1446_133_0_0
15/12/2006 13:59:23|rosetta@home|Finished upload of file s018__BOINC_LOOP_RELAX_IGNORE_THE_REST_hom001__IGNORE_THE_REST_mapback_hom009_S_00002_0004955_0_1446_133_0_0
15/12/2006 13:59:23|rosetta@home|Throughput 18793 bytes/sec
15/12/2006 16:02:35|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
15/12/2006 16:02:35|rosetta@home|Reason: To fetch work
15/12/2006 16:02:35|rosetta@home|Requesting 21600 seconds of new work, and reporting 1 completed tasks
15/12/2006 16:02:40|rosetta@home|Scheduler request succeeded
15/12/2006 16:02:40|rosetta@home|Message from server: No work sent
15/12/2006 16:02:40|rosetta@home|Message from server: (there was work but you don't have enough disk space allocated)
15/12/2006 16:02:40|rosetta@home|Message from server: BOINC will delete file SASA-masks.dat.gz when no longer needed
15/12/2006 16:02:40|rosetta@home|Got server request to delete file SASA-masks.dat.gz
15/12/2006 16:02:40|rosetta@home|No work from project
15/12/2006 16:34:07|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
15/12/2006 16:34:07|rosetta@home|Reason: Requested by user
15/12/2006 16:34:07|rosetta@home|Requesting 21600 seconds of new work
15/12/2006 16:34:12|rosetta@home|Scheduler request succeeded
15/12/2006 16:34:12|rosetta@home|Message from server: No work sent
15/12/2006 16:34:12|rosetta@home|Message from server: (there was work but you don't have enough disk space allocated)
15/12/2006 16:34:12|rosetta@home|Message from server: BOINC will delete file Paa.gz when no longer needed
15/12/2006 16:34:12|rosetta@home|Got server request to delete file Paa.gz
15/12/2006 16:37:06||Rescheduling CPU: project reset by user
15/12/2006 16:37:06|rosetta@home|Resetting project
15/12/2006 16:37:06||Rescheduling CPU: exit_tasks
15/12/2006 16:41:19|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
15/12/2006 16:41:19|rosetta@home|Reason: Requested by user
15/12/2006 16:41:19|rosetta@home|Requesting 21600 seconds of new work
15/12/2006 16:41:24|rosetta@home|Scheduler request succeeded
15/12/2006 16:41:24|rosetta@home|Message from server: No work sent
15/12/2006 16:41:24|rosetta@home|Message from server: (there was work but you don't have enough disk space allocated)
15/12/2006 16:41:24|rosetta@home|Message from server: BOINC will delete file Paa_n.gz when no longer needed
15/12/2006 16:41:24|rosetta@home|Got server request to delete file Paa_n.gz
15/12/2006 16:41:38|rosetta@home|Resetting project
15/12/2006 16:41:38||Rescheduling CPU: exit_tasks
15/12/2006 16:41:38|rosetta@home|Detaching from project
15/12/2006 16:41:38||Rescheduling CPU: project detached by user

---

Just re-attached my linux host and all 5.43 wu's went wrong.

Some even froze up the manager, others just had a compute error.

Manager 5.7.5 Linux

Some massages:

<core_client_version>5.7.5</core_client_version>
<![CDATA[
<message>
Maximum memory exceeded
</message>
]]>

<core_client_version>5.7.5</core_client_version>
<![CDATA[
<message>
Maximum memory exceeded
</message>
<stderr_txt>
Graphics are disabled due to configuration...
# random seed: 2307412
SIGSEGV: segmentation violation
Stack trace (20 frames):
[0x8ab6403]
[0x8ace4bc]
[0xffffe420]
[0x88dac6f]
[0x88dfec3]
[0x8955e10]
[0x8958733]
[0x86d29a8]
[0x86d9781]
[0x86daf13]
[0x842fc1b]
[0x84305ba]
[0x88bd312]
[0x88c0117]
[0x80dc90d]
[0x84d61db]
[0x85eb303]
[0x85eb3ac]
[0x8b2d9d4]
[0x8048111]

Exiting...

</stderr_txt>
]]>

;-)

---

Looks like the new memory managment is kicking in on your computer Rene.
afaik it is doing as it should, you would need to ask in the BOINC forums about this though.

Don't know why the segfaults happened though.

---

Team mauisun.org

Could you please give a try to re-attach the project and see if the problem gets cleared out. I don't know exactly why this happens, but it looks like there was a mis-communication between your boinc mananger and our project server because the queue has been very full recently and most of them do not have special memory requirements, so it is strange to get message "no work" from the server and I am sure "not enough disk space" is one of the strange side effects from that mis-communication. Also, I noticed that all the three crashed jobs were running under 5.41 which has been known to have some graphic problems. But with new updated 5.43, the problem seems to be alleviated a lot according to the tests and reports so far. Thanks for your help and let us know if the problem gets solved.

Just had to detach from the project, tried to reschedule but no luck.

3 of the last 5 WU's froze apparently due to graphics, now the project is telling me I do not have enough space for new WU's

Attached is list of messages received to see if this is of any assistance to developers.

15/12/2006 09:18:46|rosetta@home|Resuming task s018__BOINC_LOOP_RELAX_IGNORE_THE_REST_hom001__IGNORE_THE_REST_mapback_hom009_S_00002_0004955_0_1446_133_0 using rosetta version 543
15/12/2006 12:02:29|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
15/12/2006 12:02:29|rosetta@home|Reason: To fetch work
15/12/2006 12:02:29|rosetta@home|Requesting 3150 seconds of new work
15/12/2006 12:02:33|rosetta@home|Scheduler request succeeded
15/12/2006 12:02:33|rosetta@home|Message from server: No work sent
15/12/2006 12:02:33|rosetta@home|Message from server: (there was work but you don't have enough disk space allocated)
15/12/2006 12:02:33|rosetta@home|Message from server: BOINC will delete file jump_templates_v2.dat.gz when no longer needed
15/12/2006 12:02:33|rosetta@home|Got server request to delete file jump_templates_v2.dat.gz
15/12/2006 12:02:33|rosetta@home|No work from project
15/12/2006 13:59:15||Rescheduling CPU: application exited
15/12/2006 13:59:15|rosetta@home|Computation for task s018__BOINC_LOOP_RELAX_IGNORE_THE_REST_hom001__IGNORE_THE_REST_mapback_hom009_S_00002_0004955_0_1446_133_0 finished
15/12/2006 13:59:17|rosetta@home|Started upload of file s018__BOINC_LOOP_RELAX_IGNORE_THE_REST_hom001__IGNORE_THE_REST_mapback_hom009_S_00002_0004955_0_1446_133_0_0
15/12/2006 13:59:23|rosetta@home|Finished upload of file s018__BOINC_LOOP_RELAX_IGNORE_THE_REST_hom001__IGNORE_THE_REST_mapback_hom009_S_00002_0004955_0_1446_133_0_0
15/12/2006 13:59:23|rosetta@home|Throughput 18793 bytes/sec
15/12/2006 16:02:35|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
15/12/2006 16:02:35|rosetta@home|Reason: To fetch work
15/12/2006 16:02:35|rosetta@home|Requesting 21600 seconds of new work, and reporting 1 completed tasks
15/12/2006 16:02:40|rosetta@home|Scheduler request succeeded
15/12/2006 16:02:40|rosetta@home|Message from server: No work sent
15/12/2006 16:02:40|rosetta@home|Message from server: (there was work but you don't have enough disk space allocated)
15/12/2006 16:02:40|rosetta@home|Message from server: BOINC will delete file SASA-masks.dat.gz when no longer needed
15/12/2006 16:02:40|rosetta@home|Got server request to delete file SASA-masks.dat.gz
15/12/2006 16:02:40|rosetta@home|No work from project
15/12/2006 16:34:07|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
15/12/2006 16:34:07|rosetta@home|Reason: Requested by user
15/12/2006 16:34:07|rosetta@home|Requesting 21600 seconds of new work
15/12/2006 16:34:12|rosetta@home|Scheduler request succeeded
15/12/2006 16:34:12|rosetta@home|Message from server: No work sent
15/12/2006 16:34:12|rosetta@home|Message from server: (there was work but you don't have enough disk space allocated)
15/12/2006 16:34:12|rosetta@home|Message from server: BOINC will delete file Paa.gz when no longer needed
15/12/2006 16:34:12|rosetta@home|Got server request to delete file Paa.gz
15/12/2006 16:37:06||Rescheduling CPU: project reset by user
15/12/2006 16:37:06|rosetta@home|Resetting project
15/12/2006 16:37:06||Rescheduling CPU: exit_tasks
15/12/2006 16:41:19|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
15/12/2006 16:41:19|rosetta@home|Reason: Requested by user
15/12/2006 16:41:19|rosetta@home|Requesting 21600 seconds of new work
15/12/2006 16:41:24|rosetta@home|Scheduler request succeeded
15/12/2006 16:41:24|rosetta@home|Message from server: No work sent
15/12/2006 16:41:24|rosetta@home|Message from server: (there was work but you don't have enough disk space allocated)
15/12/2006 16:41:24|rosetta@home|Message from server: BOINC will delete file Paa_n.gz when no longer needed
15/12/2006 16:41:24|rosetta@home|Got server request to delete file Paa_n.gz
15/12/2006 16:41:38|rosetta@home|Resetting project
15/12/2006 16:41:38||Rescheduling CPU: exit_tasks
15/12/2006 16:41:38|rosetta@home|Detaching from project
15/12/2006 16:41:38||Rescheduling CPU: project detached by user

---

Looks like the new memory managment is kicking in on your computer Rene.
afaik it is doing as it should, you would need to ask in the BOINC forums about this though.

Don't know why the segfaults happened though.

Keeping that in mind, I did re-attach with the following settings:

Use at most 90% of memory when computer is in use
Use at most 90% of memory when computer is idle

Default:
Use at most 50% of memory when computer is in use
Use at most 90% of memory when computer is idle

Just tried one with 100%-100% and this also failed.

<core_client_version>5.7.5</core_client_version>
<![CDATA[
<message>
Maximum memory exceeded
</message>
<stderr_txt>
Graphics are disabled due to configuration...
# random seed: 2255689
SIGSEGV: segmentation violation
Stack trace (20 frames):
[0x8ab6403]
[0x8ace4bc]
[0xffffe420]
[0x88dac6f]
[0x88dfec3]
[0x8955e10]
[0x8958733]
[0x86d29a8]
[0x86d9781]
[0x86daf13]
[0x842fc1b]
[0x84305ba]
[0x88bd312]
[0x88c0117]
[0x80dc90d]
[0x84d61db]
[0x85eb303]
[0x85eb3ac]
[0x8b2d9d4]
[0x8048111]

Exiting...
SIGSEGV: segmentation violation
SIGABRT: abort called
SIGABRT: abort called
SIGABRT: abort called
SIGABRT: abort called
SIGABRT: abort called

...... (lots more)

SIGABRT: abort called
SIGABRT: abort called
SIGABRT: abort called
SIGABRT: abort called

</stderr_txt>
]]>

Maybe it's because of the 256Mb memory of the host..?

;-)

EDIT:
Just checked the running processes and saw that 5.43 was using 17.4 Mb.
To compare: Seti 63.4 Mb and Docking 23.2 Mb.
Both Seti and Docking are running OK.

---

No problems (so far) with this host.

Pentium D 805 (windows) 1Gb memory is running 2 wu's at this moment and I can open, drag, click... both graphics screens at once.

VGA: Ati Radeon 9200 SE AGP 128Mb

;-)

---

Just installed 5.43 and tried dragging the graphics screen all around, unable to reproduce this problem. Can drag it all over my screen and enlarge and shrink to any size and it keeps on chugging away.

Oops - maybe I wasn't clear enough. No, dragging or resizing the window is NOT a problem. What crashed it, was clicking and dragging INSIDE the graphics window. To be precise, I clicked somewhere on the picture of the backbone structure inside the "ACCEPTED" box, and attempted to manipulate or rotate it by dragging to another point inside the graphics window (I think my release point may have ben outside of the "ACCEPTED" box though). As soon as I released the mouse button, the window graphics window crashed, with the usual "would you like to send a report to Microsoft", etc.

---

The mouse zooming and rotating features have been disabled in 5.43 and I don't think you can do any mouse manipulation on the graphic now. I just tried what you did on our windows computer and nothing happened as expected. Were you able to rotate the protein in any of the graphic boxes when the crash occured? Were you running 5.43 then?

Just installed 5.43 and tried dragging the graphics screen all around, unable to reproduce this problem. Can drag it all over my screen and enlarge and shrink to any size and it keeps on chugging away.

Oops - maybe I wasn't clear enough. No, dragging or resizing the window is NOT a problem. What crashed it, was clicking and dragging INSIDE the graphics window. To be precise, I clicked somewhere on the picture of the backbone structure inside the "ACCEPTED" box, and attempted to manipulate or rotate it by dragging to another point inside the graphics window (I think my release point may have ben outside of the "ACCEPTED" box though). As soon as I released the mouse button, the window graphics window crashed, with the usual "would you like to send a report to Microsoft", etc.

---

The mouse zooming and rotating features have been disabled in 5.43 and I don't think you can do any mouse manipulation on the graphic now. I just tried what you did on our windows computer and nothing happened as expected. Were you able to rotate the protein in any of the graphic boxes when the crash occured? Were you running 5.43 then?

No, indeed the protein didn't rotate. I didn't see any on screen response to the click and drag other than the crash at the end of it.

Perhaps something to do with my specific graphics config? Don't know if the following is helpful, but here's some dxdiag.exe output for my display device:

------------------
System Information
------------------
Time of this report: 12/16/2006, 01:03:37
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp.050928-1517)
Language: English (Regional Setting: English)
System Manufacturer: TOSHIBA
System Model: Satellite M105
BIOS: Ver 1.00PARTTBL0
Processor: Genuine Intel(R) CPU T2300 @ 1.66GHz (2 CPUs)
Memory: 1014MB RAM
Page File: 1312MB used, 1131MB available
Windows Dir: C:WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode

---------------
Display Devices
---------------
Card name: Mobile Intel(R) 945GM Express Chipset Family
Manufacturer: Intel Corporation
Chip type: Intel(R) Calistoga Graphics Controller
DAC type: Internal
Device Key: EnumPCIVEN_8086&DEV_27A2&SUBSYS_FF001179&REV_03
Display Memory: 128.0 MB
Current Mode: 1280 x 800 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: ialmrnt5.dll
Driver Version: 6.14.0010.4436 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 11/28/2005 22:12:08, 36990 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: ialmnt5.sys
Mini VDD Date: 11/28/2005 22:20:20, 1353820 bytes
Device Identifier: {D7B78E66-64E2-11CF-9D63-0ADFA2C2CB35}
Vendor ID: 0x8086
Device ID: 0x27A2
SubSys ID: 0xFF001179
Revision ID: 0x0003
Revision ID: 0x0003
Video Accel:
Deinterlace Caps: n/a
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Not Available
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run

---

Were you running 5.43 then?

Sorry, forgot to add - Yes, I was definitely running 5.43 at the time.

---

Philip,

The integrated Intel (945) has been listed before when graphics problems happen.

Is that using the trackpad, nipple or a mouse ?

First try the newer graphics drivers, I think there are a lot of improvments in them Intel 945GM series drivers for WinXP





P.S. Have you check to see if your battery is one of the recall (exploding Sony) ones. That laptop is on the risk list.

---

Team mauisun.org

I didn't even know about the mouse moves to the proteins in the graphics until I read that they were going bye-bye. Bummer.

My granted credit is really low with this new version and its associated work units. It's killing my RAC.

---

just for test, i have setup that setting for 2 hours and after it reached that period it just stop doing something, like the last time and get 70% done... i will increase the period to 4 hours, to have the task completed... but i think this is not a solution... the watch dog is not restarting the application, it just keep it in memory while it is not doing nothing... the other applications are working properly... i think someone should verify this... i am not using graphics also...

---

12/15/2006 12:10:20 PM|rosetta@home|Unrecoverable error for result BAK_1avs_TnC_loop_model_1438_14802_0 ( - exit code -1073741819 (0xc0000005))

12/15/2006 7:53:42 PM|rosetta@home|Unrecoverable error for result BAK_1avs_TnC_loop_model_1438_22549_0 ( - exit code -1073741819 (0xc0000005))

I am certain the screen was "blank" the second time. I am not sure about the first.

Processor: 2 GenuineIntel Intel(R) Pentium(R) D CPU 3.40GHz
Memory: 2.00 GB physical, 3.85 GB virtual
Disk: 222.65 GB total, 178.13 GB free
Windows XP Home

---

12/16/2006 7:28:50 AM|rosetta@home|Unrecoverable error for result BAK_1avs_TnC_loop_model_1438_31605_0 ( - exit code -1073741819 (0xc0000005))

---