This is probably either because:
- Multiple instances of GRIP are running (either from multiple deployments, or from your robot program starting GRIP)
- GRIP is not garbage collecting at an appropriate rate, so it's actually running out of memory
Both of these were fixed in
v1.2.0, which was released today. Let me know if it works now.