I have a bunch of extra minirosetta_2.1 tasks that have not exited. They're just hanging around and using RAM:

hbarta@oak:~$ ps -el|grep rosetta
0 R   119 10056  1315 96  99   - - 123959 ?     ?        03:53:18 minirosetta_2.1
1 S   119 10057 10056  0  99   - - 123959 poll_s ?       00:00:00 minirosetta_2.1
1 S   119 10058 10057  0  99   - - 123959 hrtime ?       00:00:01 minirosetta_2.1
1 S   119 10059 10057  0  99   - - 123959 hrtime ?       00:00:00 minirosetta_2.1
0 R   119 10078  1315 95  99   - - 95345 ?      ?        02:56:14 minirosetta_2.1
1 S   119 10079 10078  0  99   - - 95345 poll_s ?        00:00:00 minirosetta_2.1
1 S   119 10080 10079  0  99   - - 95345 hrtime ?        00:00:01 minirosetta_2.1
1 S   119 10081 10079  0  99   - - 95345 hrtime ?        00:00:00 minirosetta_2.1
0 R   119 10102  1315 96  99   - - 90096 ?      ?        02:04:05 minirosetta_2.1
1 S   119 10103 10102  0  99   - - 90096 poll_s ?        00:00:00 minirosetta_2.1
1 S   119 10104 10103  0  99   - - 90096 hrtime ?        00:00:00 minirosetta_2.1
1 S   119 10105 10103  0  99   - - 90096 hrtime ?        00:00:00 minirosetta_2.1
0 R   119 10150  1315 86  99   - - 87666 ?      ?        00:30:51 minirosetta_2.1
1 S   119 10151 10150  0  99   - - 87666 poll_s ?        00:00:00 minirosetta_2.1
1 S   119 10152 10151  0  99   - - 87666 hrtime ?        00:00:00 minirosetta_2.1
1 S   119 10153 10151  0  99   - - 87666 hrtime ?        00:00:00 minirosetta_2.1
hbarta@oak:~$ 

Boinc Manager only shows active and ready to run tasks at the moment so these must have already been reported. (There are 7 ready to run and 12 left over tasks so these must hve completed and been reported.)

Linux - Ubuntu 10.04 LTS

hbarta@oak:~$ uname -a
Linux oak 2.6.32-29-generic #58-Ubuntu SMP Fri Feb 11 20:52:10 UTC 2011 x86_64 GNU/Linux

Boinc Manager 6.10.17 (Which comes from Ubuntu's repo.)

Suspend/resume does not clear these. "Leave applications in memory while suspended" is not checked.

Is this the right place to report this sort of behavior?

Is there any more information I need to provide?

Any particular reason for using such an old version of minirosetta?

I currently have a few workunits using 2.17.

Any particular reason for using such an old version of minirosetta?

I currently have a few workunits using 2.17.

That's a red herring. The actual executable is minirosetta_2.17_x86_64-pc-linux-gnu.

To the original question, I've seen this on other systems and happening for the first WU so I presume it indicates that there are multiple threads for each Rosetta process that I have not noticed before.

thanks,
hank

There is a thread for the "watch dog", and if you are displaying it, for the graphic. But these threads use only minor CPU time. There may be others as well, those are just two that I am aware of.

---

Rosetta Moderator: Mod.Sense