Or, at least I think this is the problem. See, Icycle2_255.swf When running one of the event handlers, we have a situation where both `currentContext.defaultTarget === null` and `currentContext.currentTarget === null`. As far as I can tell, this should never happen. The error appears in avm1GetVariable when variableName is "mbutton". currentTarget ends up being null, which then triggers an exception. I was able to reproduce the bug consistently in Chrome with the following set of patches applied: https://github.com/mozilla/shumway/pull/1884

Should be investigated as it has the potential to affect lots of content. If it isn't fixed by now.

This works. As the game does to a substantial extent: the intro looks exactly right to me, and the first level is fully playable. Well, except for being *really* slow - which the intro wasn't. So all in all, a pretty nice improvement.