I have only seen about 3 or 4 WUs crash on my mac mini since I started it here last year but several 1.67 WUs have crashed recently. My other computers are doing the same thing too so is this happening to anyone else or just me? EDIT Also I forgot to say that these were in my logs after a few of the crashes on both my mini and P4 machine
Wed May 13 18:29:25 2009 rosetta@home Task ccf_fair_filt_0.5_chunk_1_8_hb_t360__IGNORE_THE_REST_1PKLA_4_10673_40_0: no shared memory segment
and
Wed May 13 18:29:25 2009 rosetta@home Task ccf_fair_filt_0.5_chunk_1_8_hb_t360__IGNORE_THE_REST_1PKLA_4_10673_40_0 exited with zero status but no 'finished' file

Check the Problems with Minirosetta Version 1.67 thread and you will see that a number of Mac users have reported problems with the latest version.

---

I have only seen about 3 or 4 WUs crash on my mac mini since I started it here last year but several 1.67 WUs have crashed recently. My other computers are doing the same thing too so is this happening to anyone else or just me? EDIT Also I forgot to say that these were in my logs after a few of the crashes on both my mini and P4 machine
Wed May 13 18:29:25 2009 rosetta@home Task ccf_fair_filt_0.5_chunk_1_8_hb_t360__IGNORE_THE_REST_1PKLA_4_10673_40_0: no shared memory segment
and
Wed May 13 18:29:25 2009 rosetta@home Task ccf_fair_filt_0.5_chunk_1_8_hb_t360__IGNORE_THE_REST_1PKLA_4_10673_40_0 exited with zero status but no 'finished' file

THe shared memory segment issue on the mac can be fixed if you are up for some shell work. The problem is that the Mac OS does not allocate very much for this important segment of memory and BOINC uses it a lot. There are directions for increasing the value but it requires some footwork to do so.

The other error is a pure BOINC error (I believe) that can happen on any project and seemingly at random. There are some palliatives that may help. CPU use to 100 if you set it lower is one of them.