We experienced Out of Memory crashes due to the finalizer queue growing faster than its thread could process it. We experienced another problem which caused many failed requests and un-closed jclouds executors. This patch prevents the OoM when we repeat that situation. I can't figure out why this behavior was originally introduced, so I thought I'd let the community comment.
Thanks! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/243#issuecomment-31545166
