Might exist in previous builds of MMF but first time it has happened to me following the steps below and I am sure I have done this before.

Steps to reproduce:

1. Create two frames.

2. In Frame 2's Frame Editor, create an active object, renamed to A1.

3. Make A1 a global object.

4. Open Frame 1's Frame Editor and drag A1 from frame 2 into frame 1.

5. Return to Frame 2 and add an alterable value to A1, renaming it to anything you want.

6. Add a behaviour to A1 then open the behaviour event editor for it.

7. At this point you are still in Frame 2. In the Workspace toolbar where you see Frame 1 and Frame 2, expand frame 1 so that the active A1 is visible in the list.

8. Click on A1 in Frame 1 and add another Alterable Value, rename it to anything you want (I double click it to rename).

9. At this stage I find that Ctrl+M does not leave the behaviour event editor and return me to the frame editor (it would usually).

10. Instead double click on Frame 1 in the Workspace toolbar which should take me to the Frame editor for Frame 1. Instead MMF crashes.


If it does not crash, open the Event Behaviour in A1 again and repeat from step 7. So far I am able to replicate this in my game and in a test app. I can upload my test app when I get home tonight if you need it, but you should be able to replicate the crash using the steps above.