many gecko-t-win* instances are staying alive long after they have stopped taking on tasks thus wasting ec2 resources. g-w should halt its host instance after a configurable period of time and after a sane default (15 minutes?) if no configuration setting exists.
This must be a bug - it should already be doing this. I'll hop on a worker and see if I can figure out why it isn't doing that.
Have you seen any more occurrences of this? I believe this is fixed with the new refactoring of the generic worker.
yes, recent g-w releases do terminate correctly on idle