...but only with Rosetta@home. I have 2 of them on my machine right now.

I also run Predictor and it doesn't have these problems (it just has problems with the project going down, etc.)

Best regards,
Bob

You may find one or two of these, they are nothing to worry about at present, we`ve all had a share. They are becoming less frequent now !

---

Not all Czech`s bounce but I`d like to try with Barbar ;-)

Make no mistake This IS the TEDDIES TEAM.

I have been experiencing this problem with between 90-95% of my WU, what happens with the credits in this situation?

---

...but only with Rosetta@home. I have 2 of them on my machine right now.

I also run Predictor and it doesn't have these problems (it just has problems with the project going down, etc.)

Best regards,
Bob

I just had two Computation errors on my PC too.

Speaking of P@H.... I get very little work from them. In fact last WU's from them was a week ago!

---

"Life is like an Ice Cream cone, just when you think you got it licked, it drips all over you!"

I had the majority of my Rosetta workunits failing until I selected "Yes" for "Leave applications in memory while preempted?" in General Preferences.

This problem and solution have been reported here previously. On my machines, it only seems to affect Rosetta, as I've never had any problems with other BOINC apps. If I turn this preference off, those other apps still complete successfully, while Rosetta throws a memory protection violation error.

I'd like to see a fix, as leaving all of these apps in memory causes more virtual memory swapping while I'm working. But I'm putting up with this bug in the name of science... ;)

Jim

I have had three in the past 24 hours. Not sure why, I will try the leaving apps in memory thing and see how it goes.

---

I had the majority of my Rosetta workunits failing until I selected "Yes" for "Leave applications in memory while preempted?" in General Preferences.

This problem and solution have been reported here previously. On my machines, it only seems to affect Rosetta, as I've never had any problems with other BOINC apps. If I turn this preference off, those other apps still complete successfully, while Rosetta throws a memory protection violation error.

I'd like to see a fix, as leaving all of these apps in memory causes more virtual memory swapping while I'm working. But I'm putting up with this bug in the name of science... ;)

Jim

Leaving the application in memory while preempted fixed all my "computational" errors. Thanks for sharing the fix!!!!! This has been annoying me for months.

---

I've got one machine PIII/1Ghz/Win2K that has errored every WU it got in the past week.

All my other machines have a few, occasional, errors. They range from PII/400/Win98se to a mix of P4/W2K to a P4/3.0/XPPro - All set to "Leave in Memory"

For the life of me, I cannot figure out why the one W2K machine has problems

---

Leaving the application in memory while preempted fixed all my "computational" errors. Thanks for sharing the fix!!!!! This has been annoying me for months.

This is actually posted as a system requirement for Rosetta.

The main problem is that this is a global BOINC setting, so if you run multiple applications, they *all* must stay memory-resident. I hope that the Rosetta development team will consider more-frequent checkpointing so that this requirement can be dropped.

Jim

The main problem is that this is a global BOINC setting, so if you run multiple applications, they *all* must stay memory-resident. I hope that the Rosetta development team will consider more-frequent checkpointing so that this requirement can be dropped.

Jim

i know this was one of the things on there to do list.

personaly i have normaly 5 or so projects on each computer and i dont have a problem with leave in memory for me at least. but yes it would be nice to have this changed so you didnt HAVE to leave in memory.

---

I just had 7 jobs and out of the 7 had 4 computation errors and have all mine set to leave in memory also just checked again and have another one says computation error. thanks

---

Visit us at Christianboards.org

I have been getting those Computation Error messages too.
Only rosetta@home throws them. Other applications seem to run smoothly.
I am implementing the tip thrown by peers here on leaving applications in memory and waiting for a couple of units to flow.
I suppose this is a local mishap.
right?

regards.

---

actualy LEAVE in MEMORY is a system requirement it is not a patch or fix.. its a requirement. im wondering how many people dont realize this?

---

actualy LEAVE in MEMORY is a system requirement it is not a patch or fix.. its a requirement. im wondering how many people dont realize this?

Leave in memory is a workaround for a bug. Hopefully the project staff will get this bug fixed eventually.

---

BOINC WIKI

BOINCing since 2002/12/8

actualy LEAVE in MEMORY is a system requirement it is not a patch or fix.. its a requirement. im wondering how many people dont realize this?

If it was an actual requirement (rather than a work around ;)) then it shouldn't be an option to disable it...

If it was an actual requirement (rather than a work around ;)) then it shouldn't be an option to disable it...

Question:

since this option is in the general preferences can a project diable the option when other projects allow it?

---

Just saw this...

Is this where this toppic is all about?

I just added a new project and now this started to happen...

11-2-2006 16:29:46|SZTAKI Desktop Grid|Successfully attached to SZTAKI Desktop Grid
[...] and a little later....
11-2-2006 16:29:57||request_reschedule_cpus: files downloaded
11-2-2006 16:29:57|rosetta@home|Pausing result BARCODE_30_1cc8A_299_27508_1 (removed from memory)
11-2-2006 16:29:57|boincsimap|Starting result 200602093.006054_0 using simap version 507
11-2-2006 16:29:58|rosetta@home|Unrecoverable error for result BARCODE_30_1cc8A_299_27508_1 ( - exit code -1073741819 (0xc0000005))
11-2-2006 16:29:58||request_reschedule_cpus: process exited
11-2-2006 16:29:58|rosetta@home|Computation for result BARCODE_30_1cc8A_299_27508_1 finished

I used to have the leave in memory setting on, but it seems now it is off... How did that happen?

this is what was in the log earlier today:
11-2-2006 7:45:57||request_reschedule_cpus: files downloaded
11-2-2006 7:45:57|rosetta@home|Pausing result BARCODE_30_1fna__299_27475_0 (left in memory)
11-2-2006 7:45:58|SETI@home|Starting result 12dc03ab.10273.9408.128420.1.68_0 using setiathome version 418
11-2-2006 9:15:58|rosetta@home|Resuming result BARCODE_30_1fna__299_27475_0 using rosetta version 481
11-2-2006 9:15:58|SETI@home|Pausing result 12dc03ab.10273.9408.128420.1.68_0 (left in memory)
11-2-2006 9:21:58||request_reschedule_cpus: process exited
11-2-2006 9:21:58|rosetta@home|Computation for result BARCODE_30_1fna__299_27475_0 finished

---

You will need to set "leave in memory" on all projects. It is a global preference, so the last project you have contacted that had general preference updates will overrule whatever you had previously set. In this case, not changing it at SZTAKI overwrote your Rosetta preference.
Just another BOINC-ism that wasn't exactly thought through.

Just saw this...

Is this where this toppic is all about?

I just added a new project and now this started to happen...

11-2-2006 16:29:46|SZTAKI Desktop Grid|Successfully attached to SZTAKI Desktop Grid
[...] and a little later....
11-2-2006 16:29:57||request_reschedule_cpus: files downloaded
11-2-2006 16:29:57|rosetta@home|Pausing result BARCODE_30_1cc8A_299_27508_1 (removed from memory)
11-2-2006 16:29:57|boincsimap|Starting result 200602093.006054_0 using simap version 507
11-2-2006 16:29:58|rosetta@home|Unrecoverable error for result BARCODE_30_1cc8A_299_27508_1 ( - exit code -1073741819 (0xc0000005))
11-2-2006 16:29:58||request_reschedule_cpus: process exited
11-2-2006 16:29:58|rosetta@home|Computation for result BARCODE_30_1cc8A_299_27508_1 finished

I used to have the leave in memory setting on, but it seems now it is off... How did that happen?

this is what was in the log earlier today:
11-2-2006 7:45:57||request_reschedule_cpus: files downloaded
11-2-2006 7:45:57|rosetta@home|Pausing result BARCODE_30_1fna__299_27475_0 (left in memory)
11-2-2006 7:45:58|SETI@home|Starting result 12dc03ab.10273.9408.128420.1.68_0 using setiathome version 418
11-2-2006 9:15:58|rosetta@home|Resuming result BARCODE_30_1fna__299_27475_0 using rosetta version 481
11-2-2006 9:15:58|SETI@home|Pausing result 12dc03ab.10273.9408.128420.1.68_0 (left in memory)
11-2-2006 9:21:58||request_reschedule_cpus: process exited
11-2-2006 9:21:58|rosetta@home|Computation for result BARCODE_30_1fna__299_27475_0 finished

---

Proudly Banned from Predictator@Home and now Cosmology@home as well. Added SETI to the list today. Temporary ban only - so need to work harder :)



"You can't fix stupid" (Ron White)