Hey guys. I run 5 different boinc projects. rosetta is the only one with failing work units. Just to double check I tested my system stability with prime95 for atleast 5+ hours (i think it was 8) and it was fine! Anyways, it's the same error code every time....Right now my log has been cleaned so I don't have the code, but the next time a work unit fails, I'll post back with the code (sorry...wouldn't have planned on posting till I had the message, which I did, but apparently my log was refreshed. Anyways..if anyone has any generic ideas, I'd love to try them and see if we can stop another work unit from failing :) (not a heat issue, not overclocked, and stable running prime95 torture test and all other projects)

---

If you do not have leave in memory checked you might want to try that....

---

BOINC Wiki

so you're saying that if I don't allow the app to remain resident in memory that it's going to cause failures like this? That seems kind of absurd considering it only runs 12.5% of the time. How much memory is sitting there being used by rosetta doing nothing the other 87.5% of the time? If you really think it'll help, I'll give it a shot, but is this just an odd problem with me or does everyone suffer from this? (by the way, none of the other projects stay resident in memory either and this is the only one with problems at the moment!)

---

<core_client_version>5.2.7</core_client_version>
<message> - exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
No heartbeat from core client for 31 sec - exiting

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x7C911E58 read attempt to address 0xBD8B111B

Exiting...

</stderr_txt>

that's the error message i got off my account page here on rosetta!

by the way..I have graphics disabled!

---

so you're saying that if I don't allow the app to remain resident in memory that it's going to cause failures like this? That seems kind of absurd considering it only runs 12.5% of the time. How much memory is sitting there being used by rosetta doing nothing the other 87.5% of the time? If you really think it'll help, I'll give it a shot, but is this just an odd problem with me or does everyone suffer from this? (by the way, none of the other projects stay resident in memory either and this is the only one with problems at the moment!)

It is fairly common on this project for work to error if it is not set to stay in memory. I have set my switch time long enough to give a reasonable chance of finishing before switching.

---

BOINC WIKI

BOINCing since 2002/12/8

so you're saying that if I don't allow the app to remain resident in memory that it's going to cause failures like this? That seems kind of absurd considering it only runs 12.5% of the time. How much memory is sitting there being used by rosetta doing nothing the other 87.5% of the time? If you really think it'll help, I'll give it a shot, but is this just an odd problem with me or does everyone suffer from this? (by the way, none of the other projects stay resident in memory either and this is the only one with problems at the moment!)

yes, for some reason rosetta must reside in memory.. I have the same issue... I no longer do rosetta as well as the other 6 projects I have because it was killing my computer to keep all those projects in memory, even when I do have 1 gig of ram.

---

My preferences are set to keep the application in memory. Nontheless, I've had 13 successive WUs report "Client Error" after appearing to have completed successfully. This is an incredible waste of time and energy. My computer could be processing Einstein or SETI, which have never reported failed work units. Does anyone have a clue what's going on?

---

Gravity is just a scientific theory. We should also teach the religious view that God is pushing us down.

could we copy zlib1.dll from BOINC folder to Rosetta folder?

---