Chromium processes in production stick around
There appears to be an issue where chromium processes are hanging around forever in production. This is hard to recreate, and investigation needs to be done. They take up quite a few resources, so we need to make sure they are properly killed. Either via some external loop, or by forcing the process to be killed at the end of a job (with a timeout?)