If you have time, I suggest filing a bug report with a minimal test case, in case someone has ideas or time later.
- Bruce On Thu, Mar 25, 2010 at 1:18 AM, Remy Blank <[email protected]> wrote: > For future reference, using a Python memory profiler showed that the > memory consumed by Python objects was remaining constant, so the leaked > memory is not accessible from Python and must probably be lost at the C > level. > > As a workaround, I ended up caching and re-using Label objects by font, > so that the font is never changed on a once-created Label. This reduced > the leak to a minimum. There still is some leakage, but it is acceptable > for my application, and could be due to a completely different cause. > > I'm still interested in trying to fix the leak for good, if anyone has > suggestions what to try. > > -- Remy > > -- 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.
