I seems rosetta_4.79 dislike being suspended while processing a WU. Because the 3 processes (why 3?) remains always in memory (I don't allow this in my preferences), I need to restart BOINC or kill manually rosetta process every time I unplug the supply of my laptop (of coarse, I don't allow Boinc to run while my laptop is running on batteries). I also noticed the same problem if I suspend the project manually.

I don't have this problem with my main project climateprediction.net.

I'm running Boinc 5.2.13 on SuSE 10.0.

---

Supplementary info: This problem may happens when WU ends. For my latest 2 WUs, I had to restart BOINC for WU 2452928 but everything was fine for WU 2452931. Results returned to server seems OK (no errors) for both WUs.

---

I seems rosetta_4.79 dislike being suspended while processing a WU. Because the 3 processes (why 3?)

I've heard this before, and have absolutly no idea, I can't run rosetta on my Linux box.

remains always in memory (I don't allow this in my preferences)

You need (read absolutly must) keep rosetta in memory, it's a known bug that they are trying to find.

How to access the leave Rosetta in memory option:
Rosetta@Home web site -> Returning Participants -> Your account-> Log in -> View or edit general preferences -> Edit preferences (down the bottom) -> Leave applications in memory while preempted? Check yes and click the update preferences button.

---

You need (read absolutly must) keep rosetta in memory, it's a known bug that they are trying to find.

That sounds good but not very suitable for laptop users who physical memory is often limited. If most of the time I don't even notice any degradation performance when running Boinc/Rosetta, I can barely run VMWare (alas, we still live in a Windows World) because Rosetta needs 100-150 MB of RAM and I have only 512 MB of physical RAM on my laptop.

I will finish processing my 30+ WUs but prevents Boinc downloading new WUs 'til you have found what it's going wrong with this bug.

Happy debugging!!!

---

Rosetta 4.80 fixe this troubles, trust me.

Restart the project and all will be fine.

cheers

---