.
JOGL is written almost entirely in Java and as such it does generate a small amount of garbage per frame (small wrapper objects which refer to data structures in the C heap for doing window system operations). However in any real application this allocation should be in the noise. Also given that this data is extremely short lived it will be cleaned up by fast young generation scavenges rather than provoking full GCs.
So is this something in the order of 1kbyte, 10kbytes, 100k bytes per frame? Just to get an idea.
I expect it should be on the order of 1 kilobyte or less per frame but I haven’t measured it myself. Other members of these forums have, though, and hopefully can chime in.