Run garbage collection in leak test

QuLogic · QuLogic · commit 34d7183b0d9b · 2022-04-28T02:30:56.000-04:00
Without it, checking the 'external' memory may indicate a leak even if
we've gotten rid of all our objects.
diff --git a/lib/matplotlib/tests/test_backends_interactive.py b/lib/matplotlib/tests/test_backends_interactive.py
@@ -508,6 +508,7 @@ def test_blitting_events(env):
 # The source of this function gets extracted and run in another process, so it
 # must be fully self-contained.
 def _test_figure_leak():
+    import gc
     import sys
 
     import psutil
@@ -523,12 +524,14 @@ def _test_figure_leak():
             plt.pause(t)
         plt.close(fig)
     mem = p.memory_info().rss
+    gc.collect()
 
     for _ in range(5):
         fig = plt.figure()
         if t:
             plt.pause(t)
         plt.close(fig)
+        gc.collect()
     growth = p.memory_info().rss - mem
 
     print(growth)
