[issue15632] regrtest.py: spurious leaks with -R option

Roundup Robot added the comment: New changeset dc18d73e67a5 by Stefan Krah in branch 'default': Closes #15632: regrtest.py: fix spurious refleaks due to various caches http://hg.python.org/cpython/rev/dc18d73e67a5 -- nosy: +python-dev resolution: -> fixed stage: patch review -> committe

[issue15632] regrtest.py: spurious leaks with -R option

Stefan Krah added the comment: Should we go all the way and also explicitly fill the small int cache? Integers 0-255 should be initialized already, but I'm not sure about [-5..-1] and 256. I haven't been able to create a test case for integers though. -- Added file: http://bugs.python.o

[issue15632] regrtest.py: spurious leaks with -R option

Stefan Krah added the comment: I'm attaching a test case. You're right, in test_buffer it's hard to reproduce but I've encountered the "leak" several times in the past months. Today I realized that the "leak" always occurred with format code 'c'. There's this passage in test_buffer: x = ran

[issue15632] regrtest.py: spurious leaks with -R option

Meador Inge added the comment: I know the title says spurious, but is there a way to reproduce this at all? Can I run a certain suite N times or something? How did you find the problem? -- nosy: +meador.inge ___ Python tracker

[issue15632] regrtest.py: spurious leaks with -R option

New submission from Stefan Krah: With the -R option, test_buffer.py needs an additional warm-up for the unicode_latin1 cache. Patch attached. -- components: Tests files: warm_latin1_cache.diff keywords: patch messages: 168063 nosy: skrah priority: normal severity: normal stage: patch rev