#drush

Probably something like Symfony Messenger + Drupal: Realtime Queues and Cron → is better for this anyway.

There's nothing to do. While leaking memory in long running PHP processes is, alas, all too frequent there is no need to be long running, the queue is perfectly fine to run one process for each item -- possible even in an parallel.

Is this still applicable? If so, please provide clear steps to reproduce. I don't think it's related to system.module, the queue system is in core/lib/Drupal/Queue. I couldn't find a "queue system" component so I guess base system will have to do.

Automatically closed - issue fixed for 2 weeks with no activity.

It is a great question, I haven't made or updated drush commands in a minute. You are probably looking in the right spot. the boilerplate in Drush definitely change over the years. for one thing it uses new style php attributes instead of annotations https://mglaman.dev/blog/writing-drush-commands-php-attributes

i asked the claude bot about drush 9 vs 12 or 13 and it gave me this; https://claude.ai/share/e41bca21-d38d-498c-9818-c17b286642d4

Thanks for your interest in re addressing this, it is a very good idea.