Thanks for the update Rob and thanks for fixing it in the next release On Monday, 11 January 2016 22:35:44 UTC, Ian H wrote: > > Hi > > Apologies if this an obvious mistake. I have a program that I want to > update the display once every two minutes but I it seems as if any value > over 1 for the interval in clock.schedule_interval start to consume large > amounts of memory and CPU. The simplest code I could reproduce this with is > below. > > > import pyglet > > window = pyglet.window.Window() > > def update(dt): > pass > @window.event > > def on_draw(): > window.clear() > > if __name__ == '__main__': > > pyglet.clock.schedule_interval(update, 10.0) > pyglet.app.run() > > I am running with Python 3.4.2, pyglet 1.2.4 on OS X 10.10.5 > > If I set the interval to 0.5 the memory for the process is about 46Mb with > a very low CPU and it seems to stay at that level. > > If I set the interval to 5.0 the memory starts at about 48Mb and within a > couple of minutes the cpu is moving up to 70% + and the memory is over > 80Mb. It will keep on increasing. > > The larger the interval value that I set the faster it seems to increase > in memory and CPU usage. > > Any assistance appreciated > Thanks > >
-- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
