Hi Michael, Do you know the tracemalloc module? Did you try it? It works on a regular Python (compiled in debug mode).
I would be curious to know if tracemalloc also allows you to track the memory leak. sys.getobjects() is just a list of objects. Do you have a tool written on top of it to track memory leaks? If yes, how? Victor Le mar. 16 avr. 2019 à 00:28, Michael Sullivan <su...@msully.net> a écrit : > > > The main question is if anyone ever used Py_TRACE_REFS? Does someone > > use sys.getobjects() or PYTHONDUMPREFS environment variable? > > I used sys.getobjects() today to track down a memory leak in the > mypyc-compiled version of mypy. > > We were leaking memory badly but no sign of the leak was showing up in mypy's > gc.get_objects() based profiler. Using a debug build and switching to > sys.getobjects() showed that we were badly leaking int objects. A quick > inspection of the values in question (large and random looking) suggested we > were leaking hash values, and that quickly pointed me to > https://github.com/mypyc/mypyc/pull/562. > > I don't have any strong feelings about whether to keep it in the "default" > debug build, though. I was using a debug build that I built myself with every > debug feature that seemed potentially useful. > > -sully > _______________________________________________ > 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/vstinner%40redhat.com -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ 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
