My initial foray into gloss by implementing a little classic asteroids game has proven to be very enjoyable and very successful, except for one annoying glitch.
The game will run very happily (and smoothly) for quite a while (certainly in the order of 5-10 minutes), but then suddenly the display updating will freeze. There are no errors and the main program logic is still running (and will respond to a keyboard quit event for instance). The length of time before the freeze seems to be proportional to the number of objects that have been displayed over the lifetime of the game - which makes me wonder about some kind of resource leak that is related to the number of Picture objects that are created and rendered.
I have tried to build/test GLFW instead of GLUT, but that plain refuses to render properly (only some objects seem to be rendered, and they are not scaled properly with everything being tiny and down at the bottom left of the screen).
My next step will probably be to try building and testing this on a Linux box, but in the meantime, I thought I'd reach out in case this is a known issue with an accessible work around.