pyglet has a fast memory leak - does not happen on hardy system

[robert]

The little program below leaks memory like there is no tomorrow.
it is a pruned down screen saver framework.
Do not run for too long as it will bring you xserver down.

package version is
python-pyglet 1.1.2.dfsg-1

On another machine running hardy and a package from here
https://launchpad.net/~xeiso/+archive/ppa/+build/768951

The problem does not exist.
--------------------------------------------------------------------
#!/usr/bin/python

import pyglet
import numpy

DIM_X = 600
DIM_Y = 1200

image = pyglet.image.create(DIM_Y+2, DIM_X+2,
                           pyglet.image.CheckerImagePattern())

window = pyglet.window.Window(DIM_Y+2, DIM_X+2)

rgba = "\0" * (4 * (DIM_X+2) * (DIM_Y+2))

@window.event
def on_draw():
   global image
   global rgba

   # comment out any of the two lines below and the leak goes away
   image.get_image_data().set_data('RGBA', 4 * (DIM_Y+2), rgba)
   image.blit(0, 0)

# schedule an empty update function, at 60 frames/second
pyglet.clock.schedule_interval(lambda dt: None, 1.0/60.0)

pyglet.app.run()

[Mathieu Comandon (strycore)]

Which version of Ubuntu is affected by this bug ?

[robert (robert-muth)]

Wow, I had totally forgotten about this bug.

I believe it occurred on Jaunty (the other possiblity is Intrepid).
I recently switched to Karmic - will try to reproduces it there.

On Fri, Jan 29, 2010 at 11:24 AM, Mathieu Comandon <email address hidden>wrote:

> Which version of Ubuntu is affected by this bug ?
>
> --
> pyglet has a fast memory leak - does not happen on hardy system
> https://bugs.launchpad.net/bugs/406869
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “pyglet” package in Ubuntu: New
>
> Bug description:
> The little program below leaks memory like there is no tomorrow.
> it is a pruned down screen saver framework.
> Do not run for too long as it will bring you xserver down.
>
> package version is
> python-pyglet 1.1.2.dfsg-1
>
> On another machine running hardy and a package from here
> https://launchpad.net/~xeiso/+archive/ppa/+build/768951<https://launchpad.net/%7Exeiso/+archive/ppa/+build/768951>
>
> The problem does not exist.
> --------------------------------------------------------------------
> #!/usr/bin/python
>
> import pyglet
> import numpy
>
>
> DIM_X = 600
> DIM_Y = 1200
>
> image = pyglet.image.create(DIM_Y+2, DIM_X+2,
> pyglet.image.CheckerImagePattern())
>
> window = pyglet.window.Window(DIM_Y+2, DIM_X+2)
>
> rgba = "\0" * (4 * (DIM_X+2) * (DIM_Y+2))
>
> @window.event
> def on_draw():
> global image
> global rgba
>
> # comment out any of the two lines below and the leak goes away
> image.get_image_data().set_data('RGBA', 4 * (DIM_Y+2), rgba)
> image.blit(0, 0)
>
> # schedule an empty update function, at 60 frames/second
> pyglet.clock.schedule_interval(lambda dt: None, 1.0/60.0)
>
> pyglet.app.run()
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/pyglet/+bug/406869/+subscribe
>

[Matthias Klose (doko)]

closing hardy is EOL