Say something silly, Laugh 'til it hurts, Take a risk, Sing out loud, Rock the boat, Shake things up, Flirt with disaster, Buy something frivolous, Color outside the lines, Cause a scene, Order dessert, Make waves, Get carried away, Have a great day!
This is NOT due to a lack of Java heap space but native (OS-level) memory - if anything, allocating more RAM will only make things worse (and I have personal experience with this sort of issue due to having a 32 bit OS, which can easily run into the issue of hitting the process limit, which will cause an out of memory issue but F3 very clearly showed otherwise, at least from within the JVM, indeed, I eliminated any issues by allocating less memory, to just 512 MB, which is more than enough even at higher settings, although this is unlikely to help the OP since they use the default allocation of 2 GB which is pretty much necessary to run modern versions).
Native memory allocation (mmap) failed to map 67108864 bytes for Failed to commit area from 0x00000000f2000000 to 0x00000000f6000000 of length 67108864.
The system is out of physical RAM or swap space
Reduce memory load on the system
Increase physical memory or swap space
Check if swap backing store is full Decrease Java heap size (-Xmx/-Xms)
With less than 43 MB of free swap they certainly have a cluttered system! (even if there is still enough physical RAM available Java needs enough free swap to work, the "free" physical RAM may also be due to paging, which will have a severe performance hit in any case)