STINNER Victor added the comment:
I'm no more interested to work on this issue. regrtest.patch is unstable, and I
don't know how to make it more reliable. Antoine's allocation counter is enough
right now.
--
resolution: - out of date
status: open - closed
Nick Coghlan added the comment:
Some of the changes to the way regrtest handles test cases has shown a weird
cycle in test_codecs - see issue #22166 for details.
I'll try Victor's patch to see if it's more enlightening than my hacked
together attempt.
--
Nick Coghlan added the comment:
On second thoughts, what Victor is doing isn't that different from my existing
hack - I'll lift the display code, but I'm happy with my data collection code.
One thing I did that seemed to reduce the noise substantially was to leave
tracing turned off most of
Antoine Pitrou added the comment:
Slightly unrelated, but in numba I've rewritten parallel testing and refleak
testing as regular unittest extensions (TestRunner / TestResult subclasses). It
also means you have per-test method refleak results, instead of per-test file.
See e.g.
Antoine Pitrou added the comment:
The problem is snapshots will by themselves create allocation noise: you cannot
really use tracemalloc to detect leaks, only to diagnose the leaks you have
detected.
--
nosy: +pitrou
___
Python tracker
STINNER Victor added the comment:
The problem is snapshots will by themselves create allocation noise: you
cannot really use tracemalloc to detect leaks, only to diagnose the leaks you
have detected.
It's trivial to ignore allocations done in the tracemalloc module. My
work-in-progress
Antoine Pitrou added the comment:
My work-in-progress patch uses for example these filters
If you use filters, you need to add filters for fnmatch and a couple other
things :)
--
___
Python tracker rep...@bugs.python.org
STINNER Victor added the comment:
2014-07-10 22:55 GMT+02:00 Antoine Pitrou rep...@bugs.python.org:
If you use filters, you need to add filters for fnmatch and a couple other
things :)
tracemalloc.Filter(False, tracemalloc.__file__, all_frames=True)
ignores all memory allocated directly or
STINNER Victor added the comment:
I tried different options to show the memory leaks found by tracemalloc, but
I'm not satisfied by any option. I get a lot of noise, the output is almost
useless. Randomly, between 1 and 1000 KB are allocated or released in random
files: in unittest or
STINNER Victor added the comment:
regrtest.patch is a work-in-progress patch. It shows the top 10 when the -R
option is used, ex: python -m test -R 3:3 test_sys.
--
nosy: +sahutd
___
Python tracker rep...@bugs.python.org
New submission from STINNER Victor:
Someone proposed to use the new tracemalloc module in test.regrtest, I don't
remember who. Maybe Nick Coghlan?
I tried an hack dash_R(), but the result was not reliable. I should try harder
:-)
--
components: Tests
messages: 204604
nosy: haypo,
11 matches
Mail list logo