I ran into this today too, and I originally thought exactly what Jared thought, that the JVM wasn't configured to let the java program use very much memory, but the error message states that "there is not enough memory for the Java Runtime Environment to continue".
I checked the error log, which confirmed that the system ran out of memory, not that the heap size was too small.
Unlike magnets, I got down to 46Mb free on the Driver Station before a crash occured. Interestingly, after the crash, the Driver Station window became maximized, which let me see cool debugging information about the Driver Station.
The error logs records the output of /proc/meminfo. Perhaps somebody with more linux experience could explain what's happening.
Code:
--------------- S Y S T E M ---------------
OS:Linux
uname:Linux 3.2.35-rt52-2.0.0f0 #1 SMP PREEMPT RT Tue Jun 3 20:49:19 CDT 2014 armv7l
libc:glibc 2.17 NPTL 2.17
rlimit: STACK 256k, CORE 2048k, NPROC 1852, NOFILE 4096, AS infinity
load average:2.34 0.80 0.28
/proc/meminfo:
MemTotal: 237120 kB
MemFree: 46784 kB
Buffers: 0 kB
Cached: 68316 kB
SwapCached: 0 kB
Active: 97544 kB
Inactive: 34200 kB
Active(anon): 85224 kB
Inactive(anon): 1768 kB
Active(file): 12320 kB
Inactive(file): 32432 kB
Unevictable: 28304 kB
Mlocked: 28356 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 91820 kB
Mapped: 46288 kB
Shmem: 2432 kB
Slab: 20768 kB
SReclaimable: 9904 kB
SUnreclaim: 10864 kB
KernelStack: 2120 kB
PageTables: 1372 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 187324 kB
Committed_AS: 173552 kB
VmallocTotal: 516096 kB
VmallocUsed: 19928 kB
VmallocChunk: 491452 kB
The problem isn't a too small heap size, but that the JVM isn't able to use 46mb of RAM.