This is on F22, but on F20, there’s no such issue. So, it appears that
there’s a memory leak somewhere, but not sure where.
I’d suspect the driver …
What hardware are they running this on ? (which GL driver)
Cheers,
Sylvain
Here’s info from one of the users:
Thanks for reporting the error on the mailing list.
To answer Sylvain, here’s the chipset and Mesa driver I’m using. I
suspect Dave also uses an Intel chipset.
$ glxinfo | grep -i opengl
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel® Sandybridge Mobile
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.1
(git-6ff3ae8)
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.6.1 (git-6ff3ae8)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.6.1
(git-6ff3ae8)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES
3.00
I’m not a subscriber on the mailing list and I’m unknown there, maybe
you could forward them this.
If some debug info is required such as an strace, I’ll subscribe to
their list and deal with them directly.