Can anyone give me a pointer to what precisely I might do to correct the situation. The first three suggestions do not apply: # Reduce memory load on the system # Increase physical memory or swap space # Check if swap backing store is full The situation requires a cold boot to correct and that ABSOLUTELY nothing be done in the user account except launching an X server prior to launching the application. [QUOTE] bash-4.3# ./HamSphere_4.010a Fatal error: out of memory Uncaught exception: Out of memory An earlier version of the application at least privides a logfile when it crashes Server:www.hamsphere.com:8010 OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00007f942b028000, 262144, 0) failed; error='Cannot allocate memory' (errno=12) # # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (mmap) failed to map 262144 bytes for committing reserved memory. # An error report file with more information is saved as: # /inconnu/hs_err_pid23337.log [/QUOTE] bash-4.3$ free total used free shared buff/cache available Mem: 5999704 217532 5033232 2760 748940 5392888 Swap: 7219376 0 7219376 bash-4.3$ LogFile - too long to be reasonably opened by emacs, but "cat /hs_err_pid23337.log |less" works fine but, at least to me, is not helpful. System is Slackware 14.2 on an "Ideapad 330 (17, Intel) | Durable, Easy-to-Use 17.3" (sic) ... Lenovo" disaster. Application Screenshot. -- William Henderson aka Slackrat http://billh.sdf.org/slackware.jpg 9HS5203 ON HamSphere Ham Radio
