From: rich@example.invalid   
      
   root  wrote:   
   > Thanks for responding.  I was able to ssh in and verify that the   
   > kernel was still running at the last "crash".  As I said, syslog   
   > revealed that the kernel was overloaded.  I have been focussed   
   > entirely on hardware, now I think I have to look into software.  I'm   
   > not entirely sure, but I think the trouble started after a change was   
   > made to my data gathering/cleaning software.  Some routines to   
   > process the online data were written by me in (c) many years ago.   
   > About the problems started, I replaced what I had written by software   
   > written by an accomplished javascript programmer.  That opened me up   
   > to a vulnerability of the javascript as well as node.js.   
      
   Hmm, this would give more weight to an "out of memory -- with no swap"   
   situation being what you are seeing.  A JS variant, running in Node, of   
   your C "data gathering" routines would likely be much more memory   
   hungry, and that combined with the memory hog that is chrome, might   
   have pushed the system past its present memory amount.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)