This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients levkivskyi, methane, serhiy.storchaka, vstinner
Date 2019-04-11.11:21:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Patch making check on memory block leaks stricter:

diff --git a/Lib/test/libregrtest/ b/Lib/test/libregrtest/
index 235d6bfd3a..dfadabdef6 100644
--- a/Lib/test/libregrtest/
+++ b/Lib/test/libregrtest/
@@ -130,7 +130,7 @@ def dash_R(ns, the_module, test_name, test_func):
     failed = False
     for deltas, item_name, checker in [
         (rc_deltas, 'references', check_rc_deltas),
-        (alloc_deltas, 'memory blocks', check_rc_deltas),
+        (alloc_deltas, 'memory blocks', check_fd_deltas),
         (fd_deltas, 'file descriptors', check_fd_deltas)
         # ignore warmup runs

Using this patch, at least the following tests fail:

* test_asyncio
* test_code
* test_collections
* test_contextlib
* test_contextlib_async
* test_ctypes
* test_functools
* test_multiprocessing_forkserver
* test_multiprocessing_spawn
* test_regrtest
* test_statistics
* test_typing
* test_xml_etree_c

I didn't analyze why yet. I guess that they are not real memory leaks, but more minor issue in the code checking for memory leaks. Sadly, it seems like such small glitch can cause a whole Refleak buildbot worker to fail :-(
Date User Action Args
2019-04-11 11:21:06vstinnersetrecipients: + vstinner, methane, serhiy.storchaka, levkivskyi
2019-04-11 11:21:06vstinnersetmessageid: <>
2019-04-11 11:21:06vstinnerlinkissue36560 messages
2019-04-11 11:21:06vstinnercreate