Ok I am frustrated. I think my ps3 just hung again. How come yoyo@home never causes a problem on my ps3 but this project does? My ps3 is remote far away so when it goes down it is a major hassle. I wouldnt mind except this project hangs it for all projects. I can't even debug it because it is remote. Details below about earlier hang. FYI running memstick version off website.

http://www.gpugrid.net/result.php?resultid=475769

Only debug output I have is after I had someone reboot the machine.

<bunch more of these left out for clarity>
# number of SPEs used 6
No heartbeat from core client for 30 sec - exiting
ENC
# number of SPEs used 6
No heartbeat from core client for 30 sec - exiting
ENC
# number of SPEs used 6
No heartbeat from core client for 30 sec - exiting
ENC
# number of SPEs used 6
FILE_LOCK::unlock(): close failed.: Bad file descriptor
No heartbeat from core client for 30 sec - exiting
ENC
# number of SPEs used 6
No heartbeat from core client for 30 sec - exiting
ENC
# number of SPEs used 6
No heartbeat from core client for 30 sec - exiting
ENC
# number of SPEs used 6
No heartbeat from core client for 30 sec - exiting
ENC
# number of SPEs used 6
ENC
# number of SPEs used 6
ENC
# number of SPEs used 6
B no 0 ./restart.coor ./restart.vel
B no 0 ./restart.coor ./restart.vel
B no 0 ./restart.coor ./restart.vel
B no 0 ./restart.coor ./restart.vel
B no 0 ./restart.coor ./restart.vel
B no 0 ./restart.coor ./restart.vel
B no 0 ./restart.coor ./restart.vel
B no 0 ./restart.coor ./restart.vel
B no 0 ./restart.coor ./restart.vel

Nevermind I figured out a solution the the problem. If anybody else is stuck in this situation here is what I recommend to remotely (with no access to machine) fix this and prevent problems in the future. Simply set the resource share for yoyo@home to 1000000 and this project to 1. Voila your playstation will actually be stable and able to contribute something to science.