The Dart VM shutdown patch had to be rolled back due to issues with secondary VM initialization in AOT mode. I have patched the VM issue but this patch has not been rolled into the engine. Once the patch has rolled in, the original patch has to be re-landed.

The original issue tracking the resource allocation has been re-opened and must be closed after this patch lands again.