Probably the best way to handle this, Matthew, is to open issues at bugs.python.org for each of the leaks you have found and then they can be discussed there.
And thanks for being willing to report these! On Wed, 13 Jan 2016 at 11:42 Matthew Paulson <paul...@busiq.com> wrote: > Hi: > > I've spent some time performing memory leak analysis while using Python in > an embedded configuration. > > The pattern is: > > Py_Initialize(); > > ... run empty python source file ... > > Py_Finalize(); > > > I've identified several suspect areas including dictionary maitenace in > import.c:~ 414 > > /* Clear the modules dict. */ > PyDict_Clear(modules); > /* Restore the original builtins dict, to ensure that any > user data gets cleared. */ > dict = PyDict_Copy(interp->builtins); > if (dict == NULL) > PyErr_Clear(); > PyDict_Clear(interp->builtins); > if (PyDict_Update(interp->builtins, interp->builtins_copy)) > PyErr_Clear(); > Py_XDECREF(dict); > /* Clear module dict copies stored in the interpreter state */ > > > Is there someone in the group that would like to discuss this topic. > There seems to be other leaks as well. I'm new to Python-dev, but willing > to help or work with someone who is more familiar with these areas than I. > > Thanks, > > Matt > > > -- > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/brett%40python.org >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
