Folks,

I was 2 minutes away from completing a result when I clicked the "Show graphics" button. The graphics window appeared for about a second and then the result aborted. FWIW, here is the error file:

<core_client_version>5.8.15</core_client_version>
<![CDATA[
<message>
process exited with code 131 (0x83)
</message>
<stderr_txt>
MacOS Error -5000 occured in /Volumes/Sage/BOINC_Mac/boinc/mac_build/../api/mac_icon.C line 107
MacOS Error -5000 occured in /Volumes/Sage/BOINC_Mac/boinc/mac_build/../api/mac_icon.C line 107
ar=0.941168 NumCfft=49509 NumGauss= 208412240 NumPulse= 22461443584 NumTriplet= 3220605960192
SIGSEGV: segmentation violation
Crashed executable name: setiathome_5.13_i686-apple-darwin
built using BOINC library version 5.5.0
Machine type Intel 80486
System version: Macintosh OS 10.4.8 build 8L2127
Mon Mar 5 22:28:59 2007
Stack frame backtrace:
# Flags Frame Addr Caller PC Return Address Symbol
=== === ========== ========== =====================
1 -P- 0xbfffd8b8 0x3f33fdb5
2 --- 0xbfffd8e8 0x1603310a gldInitDispatch + 0x1a80
3 --- 0xbfffd968 0x15ec0010 gleRenderSmoothQuadsFunc + 0x240
4 --- 0xbfffd988 0x15ebfda8 glEnd_Exec + 0x32
5 --- 0xbfffd9b8 0x92b0f651 glEnd + 0x4c
6 F-- 0x00000001 0x0000de18 _ZN12SAH_GRAPHICS14render_pillarsEdd + 0x74c

Thread number 2: Stack frame backtrace:
# Flags Frame Addr Caller PC Return Address Symbol
=== === ========== ========== =====================
1 F-- 0x00000000 0x90037697 mach_wait_until + 0x7
2 --- 0xb0101728 0x900374de nanosleep + 0x18e
3 --- 0xb0101768 0x90037319 sleep + 0x79
4 --- 0xb01017a8 0x00048452 _Z11boinc_sleepd + 0x22
5 --- 0xb0101f38 0x00042b78 _Z12timer_threadPv + 0x92
6 --- 0xb0101fe8 0x90023d87 _pthread_body + 0x54
7 FP- 0x00000000 0x00000000

Exiting...

</stderr_txt>
]]>

Jim

This could happens sometimes. Some users has reported this issue, too.
Did your WUs crash on every attept to show the graphics ?
So far I know will Eric has fixed this problem in the next SETI release.

---

This could happens sometimes. Some users has reported this issue, too.
Did your WUs crash on every attept to show the graphics ?
So far I know will Eric has fixed this problem in the next SETI release.

I think this has happened maybe one other time and I process a lot of WUs, so no, this is not a common eror with me.

Jim