summaryrefslogtreecommitdiffstats
path: root/Python/pylifecycle.c
diff options
context:
space:
mode:
authorŁukasz Langa <lukasz@langa.pl>2016-09-10 04:47:46 (GMT)
committerŁukasz Langa <lukasz@langa.pl>2016-09-10 04:47:46 (GMT)
commitfef7e94fa12f21c09997bd02809e677830966646 (patch)
tree2f355b7146c4eb0426b93c29ac96072824361c13 /Python/pylifecycle.c
parent9e3ef52a35c2d45edca40f9e4208aa8a08d6cdfd (diff)
downloadcpython-fef7e94fa12f21c09997bd02809e677830966646.zip
cpython-fef7e94fa12f21c09997bd02809e677830966646.tar.gz
cpython-fef7e94fa12f21c09997bd02809e677830966646.tar.bz2
Don't run garbage collection on interpreter exit if it was explicitly disabled
by the user.
Diffstat (limited to 'Python/pylifecycle.c')
-rw-r--r--Python/pylifecycle.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/Python/pylifecycle.c b/Python/pylifecycle.c
index f93afd2..5b5cc2b 100644
--- a/Python/pylifecycle.c
+++ b/Python/pylifecycle.c
@@ -600,12 +600,12 @@ Py_FinalizeEx(void)
* XXX but I'm unclear on exactly how that one happens. In any case,
* XXX I haven't seen a real-life report of either of these.
*/
- PyGC_Collect();
+ _PyGC_CollectIfEnabled();
#ifdef COUNT_ALLOCS
/* With COUNT_ALLOCS, it helps to run GC multiple times:
each collection might release some types from the type
list, so they become garbage. */
- while (PyGC_Collect() > 0)
+ while (_PyGC_CollectIfEnabled() > 0)
/* nothing */;
#endif
/* Destroy all modules */
@@ -632,7 +632,7 @@ Py_FinalizeEx(void)
* XXX Python code getting called.
*/
#if 0
- PyGC_Collect();
+ _PyGC_CollectIfEnabled();
#endif
/* Disable tracemalloc after all Python objects have been destroyed,