Hi Gary
I am new in Linux world, but have that error many times. I try to find solution on the Internet and it looks like some kind of error in Boinc manager. Every 30 seconds ( or so) Boinc check to see if application is live or not. If there is no response from application you will get that error. But that error is found in many boinc versions, and never was fixed.
I am sorry since I cannot help you more, nut that is what I know about that problem.
You may try with lower CPU freq ( if you do CPU tasks..)

____________
92*10^^1585996-1 NEAR-REPDIGIT PRIME :) :) :)
4 * 650^⁴⁹⁸¹⁰¹-1 CRUS PRIME
2022202116^¹³¹⁰⁷²+1 GENERALIZED FERMAT
Proud member of team Aggie The Pew. Go Aggie!

Running Genefer in a VMware VM is no problem. I do this on different hosts and the last Genefer unit was done on host dl380-g2.
As you can see, a 64bit linux (DotschUX/1.2) with only 448MB vRAM.


OT:
If you are using VMware Workstation, Player or Fusion (unsure, because never used), using a bunch of memory does not help in any cases. In dependence of the host-OS you will see some strange effects. If you configured the vRAM to high (depended of the product-version between 768-1500MB), your host will hold only a part of vRAM in the pRAM (mostly 300-400MB) and marked the rest as swappable. The host-OS will respond to this immediattely and ave the content of vRAM on the host swap area. Your VM-performance goes down.
Therefore exists the unwritten law for vSMP and vRAM inside a VM: Only as much as needed and not as possible!

For every virtualization product you have to do some homework.

• Disable all energy savings settings. If your host decides to go in sleepmode, he will do this and does not inform the runnings VM(s) about this in all cases. On the other side if a guest/VM decided to go in sleepmode, it can slowdown all other running VMs.
  
• Set all vDisk (VMware uses the ending VMDK) on the exception list in your antivirus-solution or security-suite. If a file is scanned by your AV-solution this file will be locked for all other processes, your VM can die or you will at least see a bluescreen.
  
• In awaiting of heavy traffic/usage inside a VM, do not start more VMs than available cores on the host minus one and let 512MB (32bit-host) or 1024MB (64bit-host) free for the host-OS. Your host-OS needs some CPU-cycles and memory for his own work. If there is no free RAM/CPU, the OS will take it independed of all other settings and the VM-performce will go down again.
  
• Using sparse-disks and/or snapshots. This type of disk is saving a lot of place on the host but fragments in shortest time and you have to shrink them manually. Using snapshots makes the same. All new written content inside a VM will be saved as a VMware sparse-disk on the host-disk and favors fragmentation...
  

____________
Best wishes. Knowledge is power. by jjwhalen