The free didn't help. If we were holding out a resource I'd expect to see the application (robot) start throwing out of memory errors, although it is possible that if the JVM is allocating memory and has been started with enough memory allocated that it's exhausting the OS's available memory it's being killed by the oom killer (beware the
oom killer!). I'm not sure if that would create a crash report.
Maybe something in /var/logs could provide a clue? Even if I find it I'm not sure we'll be able to fix it since it's in WPI's native libraries somewhere. Any thoughts on who to contact for support on the WPI lib?