No robot code after running for a while (Java VM ran out of memory)

[Cel Skeggs]

It may be helpful to note that we ran into similar issues, despite not using any vision tracking. Our diagnostics showed that it may have been an issue related to too many DirectByteBuffers being allocated. We couldn't figure out exactly why this happened, but it may be related to the fact that WPILibJ allocates a DirectByteBuffer and lets the Garbage Collector collect it ... every single time that it makes a JNI call. However, I couldn't seem to fix this by caching them, so I'm not sure if it was the issue.

It might be helpful to disable your vision tracking code to see if the problem is with vision tracking or a different part of your code.