[issue12998] Memory leak with CTypes Structure

2011-11-03 Thread Stefan Krah
Changes by Stefan Krah stefan-use...@bytereef.org: -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12998 ___ ___

[issue12998] Memory leak with CTypes Structure

2011-09-17 Thread M
New submission from M abcdefg.abcdefghijklmnopqrs...@gmail.com: When using Python 2.5.4 on Windows (and potentially other versions and platforms), usage of CTypes like the following cause a memory leak. The memory leak can be verified with ProcessExplorer, as the memory Python takes up keeps

[issue12998] Memory leak with CTypes Structure

2011-09-17 Thread M
M abcdefg.abcdefghijklmnopqrs...@gmail.com added the comment: Correction to the above link: See: http://stackoverflow.com/questions/7452625/python-ctypes-memory-leak-with-structure -- ___ Python tracker rep...@bugs.python.org

[issue12998] Memory leak with CTypes Structure

2011-09-17 Thread Alex Gaynor
Alex Gaynor alex.gay...@gmail.com added the comment: This is caused by a cache which is kept of array's for different (Structure, length) pairs. -- nosy: +alex ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12998

[issue12998] Memory leak with CTypes Structure

2011-09-17 Thread M
M abcdefg.abcdefghijklmnopqrs...@gmail.com added the comment: If it is a cache, shouldn't it be garbage-collected or limited in size? Why does it grow without bounds? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12998

[issue12998] Memory leak with CTypes Structure

2011-09-17 Thread Sebastian Wiesner
Sebastian Wiesner lunary...@googlemail.com added the comment: Why should it? After all, you're sort of abusing ctypes by repeatedly creating Struture types over and over again. C structures that you might want to wrap with these types are fixed and known at the time of programming, so there

[issue12998] Memory leak with CTypes Structure

2011-09-17 Thread Stefan Krah
Stefan Krah stefan-use...@bytereef.org added the comment: I can reproduce the leak with Python 2.5.4, but not with Python 2.6.5 or Python 3.2. Python 2.5.4 is an ancient version. Please upgrade to Python 2.7 or Python 3.2. If the leak still exists, just respond to this issue and it will be