@Ashley: I could still see this failure in r103.2. But I am not able to get a short repro for you(because of the way my project is setup and the size of it). Taking a hint from @kyatric, when I eliminated a case where an explicit Destroy and FadeOut destroy can happen on the same object, the crash is gone.

As you know C2 used to handle this in r101 fine. Would you consider fixing this?

I found and fixed the issue in @Kyatric's capx example. However since I don't have .capx files from @vnHarry or @iunkn, I cannot confirm that it is fixed for you as well, but I would think it is likely that it is fixed. This fix will go in to the next beta release (104).

Woop - I'll disable fade/destroy for now then? I thought I'd seriously broken something - I learned how to use the Chrome Console though, now it's much quicker to track down what is actually causing the error and where.