would be good to be more specific about the error, and which things you’re seeing it on, because there are particular targets that trigger this reliably due to scheduler leaks