After9bca86812857 (#22104), test_codecs now reports "leaked" references from ExceptionChainingTest.  Previously the tests were only ever loaded one time, so each run of the tests was actually using the same set of TestCase instances; now the tests are freshly loaded before every test run and thus each run uses a new set of TestCase instances.  My suspicion is that this is coming into play in ExceptionChainingTest.setUp, where the test's codec_name attribute is derived from the repr and id of the TestCase instance.  However, I'm not familiar enough with the codecs code to know where it's going wrong from there.One possible "fix" is to abuse load_tests to ensure the tests are only loaded once:_suite = Nonedef load_tests(loader, suite, pattern):    global _suite    if _suite is None:        _suite = suite    return _suite...which restores the old behavior, but strikes me as a fairly horrible hack.  Somewhat less bad would be to just skip those tests when they've already been run before.  I can't help but feel that there has to be a better solution that I can't see, though.Nick, as the original author of the test class in question, do you have any insight into a better way to fix the "leaks"?

I did a bit of poking around with tracemalloc (debugging patch diff attached)encodings._cache is definitely one culprit, but something else is going on where it appears the *test cases* are being kept alive.For comparison, with my hacked regrtest, I get this for test_cmd_line:$ ./python -m test -R 3:1 test_grammar[1/1] test_grammarbeginning 4 repetitions1234....[ Top 20 differences ]/home/ncoghlan/devel/py34/Lib/_weakrefset.py:37: size=9936 B (+9936 B), count=54 (+54), average=184 B/home/ncoghlan/devel/py34/Lib/_weakrefset.py:38: size=6696 B (+6696 B), count=54 (+54), average=124 B/home/ncoghlan/devel/py34/Lib/_weakrefset.py:48: size=6480 B (+6480 B), count=27 (+27), average=240 B/home/ncoghlan/devel/py34/Lib/mimetypes.py:487: size=6176 B (+6176 B), count=1 (+1), average=6176 B/home/ncoghlan/devel/py34/Lib/ctypes/__init__.py:272: size=2362 B (+2362 B), count=12 (+12), average=197 B/home/ncoghlan/devel/py34/Lib/ctypes/__init__.py:99: size=2167 B (+2167 B), count=11 (+11), average=197 B/home/ncoghlan/devel/py34/Lib/ctypes/__init__.py:274: size=2137 B (+2137 B), count=11 (+11), average=194 B/home/ncoghlan/devel/py34/Lib/_weakrefset.py:92: size=1944 B (+1944 B), count=27 (+27), average=72 B/home/ncoghlan/devel/py34/Lib/test/regrtest.py:1466: size=1568 B (+1568 B), count=1 (+1), average=1568 B/home/ncoghlan/devel/py34/Lib/_weakrefset.py:84: size=1344 B (+1344 B), count=14 (+14), average=96 B/home/ncoghlan/devel/py34/Lib/contextlib.py:38: size=656 B (+656 B), count=1 (+1), average=656 B/home/ncoghlan/devel/py34/Lib/unittest/suite.py:87: size=512 B (+512 B), count=1 (+1), average=512 B/home/ncoghlan/devel/py34/Lib/test/support/__init__.py:1735: size=488 B (+488 B), count=1 (+1), average=488 B/home/ncoghlan/devel/py34/Lib/mimetypes.py:534: size=416 B (+416 B), count=1 (+1), average=416 B/home/ncoghlan/devel/py34/Lib/mimetypes.py:384: size=416 B (+416 B), count=1 (+1), average=416 B/home/ncoghlan/devel/py34/Lib/test/regrtest.py:1475: size=224 B (+224 B), count=1 (+1), average=224 B/home/ncoghlan/devel/py34/Lib/test/regrtest.py:1464: size=224 B (+224 B), count=1 (+1), average=224 B/home/ncoghlan/devel/py34/Lib/mimetypes.py:387: size=224 B (+224 B), count=1 (+1), average=224 B/home/ncoghlan/devel/py34/Lib/linecache.py:31: size=224 B (+224 B), count=1 (+1), average=224 B/home/ncoghlan/devel/py34/Lib/ctypes/__init__.py:103: size=224 B (+224 B), count=1 (+1), average=224 Btest_grammar leaked [-3] references, sum=-31 test failed:    test_grammarWhile for test_codecs I get this:$ ./python -m test -R 3:1 test_codecs[1/1] test_codecsbeginning 4 repetitions1234....[ Top 20 differences ]/home/ncoghlan/devel/py34/Lib/unittest/case.py:408: size=83.7 KiB (+83.7 KiB), count=206 (+206), average=416 B/home/ncoghlan/devel/py34/Lib/unittest/case.py:368: size=41.8 KiB (+41.8 KiB), count=411 (+411), average=104 B/home/ncoghlan/devel/py34/Lib/unittest/case.py:387: size=16.1 KiB (+16.1 KiB), count=206 (+206), average=80 B/home/ncoghlan/devel/py34/Lib/unittest/suite.py:60: size=14.5 KiB (+14.5 KiB), count=206 (+206), average=72 B/home/ncoghlan/devel/py34/Lib/unittest/case.py:381: size=13.6 KiB (+13.6 KiB), count=174 (+174), average=80 B/home/ncoghlan/devel/py34/Lib/test/test_codecs.py:2653: size=12.2 KiB (+12.2 KiB), count=2 (+2), average=6242 B/home/ncoghlan/devel/py34/Lib/test/regrtest.py:1475: size=12.0 KiB (+12.0 KiB), count=1 (+1), average=12.0 KiB/home/ncoghlan/devel/py34/Lib/_weakrefset.py:37: size=9936 B (+9936 B), count=54 (+54), average=184 B/home/ncoghlan/devel/py34/Lib/unittest/loader.py:156: size=7600 B (+7600 B), count=95 (+95), average=80 B/home/ncoghlan/devel/py34/Lib/_weakrefset.py:38: size=6696 B (+6696 B), count=54 (+54), average=124 B/home/ncoghlan/devel/py34/Lib/_weakrefset.py:48: size=6480 B (+6480 B), count=27 (+27), average=240 B/home/ncoghlan/devel/py34/Lib/mimetypes.py:487: size=6176 B (+6176 B), count=1 (+1), average=6176 B/home/ncoghlan/devel/py34/Lib/unittest/case.py:625: size=3232 B (+3232 B), count=4 (+4), average=808 B/home/ncoghlan/devel/py34/Lib/test/test_codecs.py:2637: size=2964 B (+2964 B), count=6 (+6), average=494 B/home/ncoghlan/devel/py34/Lib/test/support/__init__.py:1739: size=2432 B (+2432 B), count=32 (+32), average=76 B/home/ncoghlan/devel/py34/Lib/ctypes/__init__.py:272: size=2362 B (+2362 B), count=12 (+12), average=197 B/home/ncoghlan/devel/py34/Lib/unittest/loader.py:70: size=2304 B (+2304 B), count=32 (+32), average=72 B/home/ncoghlan/devel/py34/Lib/unittest/suite.py:125: size=2168 B (+2168 B), count=7 (+7), average=310 B/home/ncoghlan/devel/py34/Lib/ctypes/__init__.py:274: size=2137 B (+2137 B), count=11 (+11), average=194 B/home/ncoghlan/devel/py34/Lib/ctypes/__init__.py:99: size=2071 B (+2071 B), count=10 (+10), average=207 Btest_codecs leaked [5602] references, sum=5602test_codecs leaked [1056] memory blocks, sum=10561 test failed:    test_codecs

Still not sure what is going on, but I tweaked my tracemalloc hacks based on Victor's draft patch in 19816 (his are designed to make this optional, where mine are hardcoded. I also sort by number of allocations, rather than amount of memory)

I assigned this to myself when I thought this was going to be an easy fix (since I knew encodings._cache wasn't getting cleared), but it looks substantially more complicated than that.I checked the codec entry was getting cleared by tearDown() correctly, and explicitly clearing the cycle between the test case and the codec implementation didn't help anything.Restoring the cache to its original state did help, but only a little bit.It may be one of the other test cases that's the problem, or else there may be something genuinely odd going on with the exception chaining and local variables.

ExceptionChainingTest uses a function to raise an arbitrary exception. Problem: the function and its parameter becomes part of the exception traceback. Shortly, the exception links indirectly to itself in a nice reference cycle...Example:---import tracebackclass Err(Exception):    def __del__(self):        print("del")def raise_exc(exc):    raise exce = Err()try:    raise_exc(e)except Exception as e:    t = e.__traceback__#traceback.clear_frames(t)e = Noneprint("exit")---Uncommand the call the clear_frames() to see the exception deleted before the exit.

Attached: Draft patch to fix some reference leaks in test_codecs.

ExceptionChainingTest creates a random codec name. If you change the codec name to a fixed string like "xxx", ExceptionChainingTest.test_raise_by_type() doesn't leak anymore (when  test_codecs_fix1.patch is applied), but other tests start to fail.We should maybe enhance the codecs API to be able to unregister a codec?

> We should maybe enhance the codecs API to be able to unregister a codec?That would be nice. At least as a private API in 3.4.

Yeah, the unique name was a hack to deal with the fact I couldn't unregister anything.As a simpler short term fix for the reference leak, perhaps it would be worth trying a call to "traceback.clear_frames(caught)" as a new final line in ExceptionChainingTest.assertWrapped?

Ah, I think I've found a possible underlying culprit: there's a separate C level "codec_search_cache" on the interpreter object that is independent of encodings._cache.The attached patch eliminates the reference leaks entirely (using gc.get_referrers() to get a reference to the otherwise inaccessible internal interpreter cache).However, the patch has a bunch of changes that may not be necessary if that cache is dealt with properly, so I'm going to revert everything, and *start* with fixing the cache cleanup.

Yep, it looks like the mess with the reference cycles in the tracebacks was just a secondary problem: the real culprit was the internal cache keeping everything else alive.Attached patch just adds clearing encodings._cache and the CPython internal cache to the ExceptionChainingTest.tearDown() method.The latter is accomplised via gc.get_referrers() and popping the codec's name from any dict remaining in that list after clearing the known caches, so it will actually handle any hidden name based caches on any interpreter.

I'd much rather see a private function somewhere (in the _codecs module) to clear that private interpreter cache.

Yeah, I'm wary of the GC hack as well. It's a nice way to prove that this the internal cache is the problem, but probably not something we want to commit.A "codecs._forget_codec" helper in the C module would be all that was needed to handle it. Other implementations could then also use that to clear their own internal cache (if they have one).

On 06.09.2014 15:03, Nick Coghlan wrote:> A "codecs._forget_codec" helper in the C module would be all that was needed to handle it. Other implementations could then also use that to clear their own internal cache (if they have one).If you want to take that approach, please call that functioncodecs._clear_lookup_cache() and also add a new C API_PyCodecRegistry_ClearLookupCache() toPython/codecs.c.Thanks,-- Marc-Andre LemburgeGenix.com

May be just do not use the unique name?

This investigation also showed why the original tests that used anon-unique name didn't work: the codec was getting cached the first timethrough and hence not seeing the different codecs registered by other tests.MAL, my plan was to provide an API to forget a specific named codec ratherthan flush the whole cache. I agree a private C API would also be a goodidea, though.

On 06.09.2014 21:14, Nick Coghlan wrote:> > This investigation also showed why the original tests that used a> non-unique name didn't work: the codec was getting cached the first time> through and hence not seeing the different codecs registered by other tests.> > MAL, my plan was to provide an API to forget a specific named codec rather> than flush the whole cache. I agree a private C API would also be a good> idea, though.I don't think such a specific API for only forgetting a single codecis useful outside this particular test case, since you typicallydon't know the names of the cached codecs.

Well, the point here is to add a private API just for our test suite, not something users would want to call.

Targeted API to forget a particular codec name.Normally we don't care about the caching (as evidenced by the fact it took 14+ years to want this feature).The intent with this API is to be able to selective purge a particular codec when we either care about getting the latest version of a specific codec (no current use cases) or to avoid the appearance of leaking references when looking up lots of custom codecs (this case).I considered dropping the per-test naming scheme, but decided I liked the fact it kept these test instances orthogonal, even though they all use the shared TEST_CODECS registry. The lack of global side effects is also a benefit of just popping the named codec, rather than purging the entire cache.

New changesetfcf45ec7863e by Nick Coghlan in branch '3.4':Issue#22166: clear codec caches in test_codecshttps://hg.python.org/cpython/rev/fcf45ec7863eNew changeset322ee2f2e922 by Nick Coghlan in branch 'default':Merge fix for issue#22166 from 3.4https://hg.python.org/cpython/rev/322ee2f2e922

IMO test_codecs_fix1.patch is still needed.Review of Nick's change:+    interp = PyThreadState_GET()->interp;+    if (interp->codec_search_path == NULL) {+        return -1;+    }I don't think that this line raises an exception. You should use an assertion here (or raises an exception, but it would be overkill).+        encodings._cache.pop(self.codec_name, None)+        try:+            _forget_codec(self.codec_name)+        except KeyError:+            passYou may move these lines to a private encoding._forget() function.By the way, codecs._forget() should maybe catch and ignore KeyError?>          _TEST_CODECS.pop(self.codec_name, None)This line may be moved to set_codec() using self.addCleanup(). (Well, it's not directly related to your change.)

On 15.09.2014 15:19, STINNER Victor wrote:> > STINNER Victor added the comment:> > IMO test_codecs_fix1.patch is still needed.> > Review of Nick's change:> > +    interp = PyThreadState_GET()->interp;> +    if (interp->codec_search_path == NULL) {> +        return -1;> +    }> > I don't think that this line raises an exception.Agreed.Please also add some documentation to the codecs.h file andperhaps a test for the function itself ;-)

Victor, would you be willing to take over pushing this one forward? I believe you have a much better idea of what's still needed than I do.

Do you mind to create a PR Victor?

> Do you mind to create a PR Victor?I completely forgot this issue and I don't plan to fix it in the short-term. Feel free to write PR if you want.

For 3.7 and 3.8, I have just tried with this command to find leaks in the test_codec* but nothing :/./python -m test -v -l -R 6:6 -u all \    test_codecencodings_iso2022 \    test_codecs \    test_codecmaps_hk test_codecmaps_tw \    test_codecencodings_tw \    test_codecencodings_cn \    test_codeccallbacks \    test_codecencodings_hk \    test_codecencodings_jp \    test_codecencodings_kr \    test_codecmaps_jp \    test_codecmaps_cn \    test_codecmaps_krIf you have another technic for the detection of leaks, please inform me but I think this issue could be closed maybe we have fixed the issue with time.

Codec tests don't leak anymore. I lost track of this very old issue. I don't think that anything should be done. Python code base changed a lot since 2014. I close the issue.