On Jun 4, 10:20 pm, "Alex Holkner" <[EMAIL PROTECTED]> wrote: > Thanks, good catch. The problem was a memory leak in pyglet.clock, > now fixed in r2100.
Cheers for the quick response, however I'm seeing the exact same behaviour with r2100. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
