Ansible controller exponential memory usage when using handler listeners in collection about ansible HOT 5 CLOSED

Looks like we just need to ensure we are operating on a copy of the handler.listen list before extending it for evaluation:

I was wondering if we could/should take it a step further and just do the work of validating/extending listen just once on task validation since listen is static #83400?

from ansible.

Looks like we just need to ensure we are operating on a copy of the handler.listen list before extending it for evaluation:

diff --git a/lib/ansible/plugins/strategy/__init__.py b/lib/ansible/plugins/strategy/__init__.py
index efd69efe9b..9cba974d07 100644
--- a/lib/ansible/plugins/strategy/__init__.py
+++ b/lib/ansible/plugins/strategy/__init__.py
@@ -558,7 +558,7 @@ class StrategyBase:
                     handler.fattributes.get('listen'),
                     listeners,
                     templar,
-                )
+                ).copy()
                 if handler._role is not None:
                     for listener in listeners.copy():
                         listeners.extend([

from ansible.

Seems like that suggested fix works.
playbook_output.txt

from ansible.

Files identified in the description:

None

If these files are incorrect, please update the component name section of the description or use the component bot command.

from ansible.

Since this problem affects 2.17 as well as 2.18, it would be great if whichever PR is chosen is a candidate for backporting. I can't really tell whether @mkrizek 's #83400 or @ShawnHardwick 's #83393 is more or less of a candidate for that, just mentioning it since it's important to us and affecting all of our internal collection testing.

from ansible.