[General Battuta]

I believe I have made some progress towards reproing the infamous right-click-on-event crash in FRED. It appears most likely to happen if you attempt to rename a new event after changing its position in the events list (for example, dragging towards top.)

more news as it develops

[Spoon]

I never ever drag events up or down, and I've had fred crash on right click
Then again, I haven't had this crash all that much recently anymore

[General Battuta]

I haven't either and I agree with your conditions, but I think this may be a way to encourage it to happen (if we needed to do that for whatever reason).

[Snail]

Like Spoon, I never drag events around and still get this error.

It could have something to do with "Insert Event"?

[General Battuta]

It's definitely* most likely to occur on a new event.

*probably definitely

[TopAce]

In my observation, you shouldn't create more than one or at most two new events without closing the events window and saving. The third or forth event made in a row will most likely crash.

I've been following the "Create event --> close --> save --> Event Editor --> Repeat" policy for a good while now, and it hasn't resurfaced. (Well, it did once, when I violated the above rule-of-thumb policy.)

As for moving around events, it's safe, in a word processor, not in FRED.

It's definitely* most likely to occur on a new event.

*probably definitely

Agreed here.

[General Battuta]

In my observation, you shouldn't create more than one or at most two new events without closing the events window and saving. The third or forth event made in a row will most likely crash.

This is my observation too, except that I don't think I'd say 'most likely' - I can routinely get through strings of renaming eight or nine events in a row without crashing. I just do it immediately after saving so I won't lose anything if I crash.

I've been following the "Create event --> close --> save --> Event Editor --> Repeat" policy for a good while now, and it hasn't resurfaced. (Well, it did once, when I violated the above rule-of-thumb policy.)

See, this is a good policy that I usually follow, but when missions break the 400kb mark it starts taking 30s to several minutes just to close the events editor, so this becomes an incredible pain in the ass.

[Droid803]

It hasn't happened as much now, but previously, it happened more when the events created were closer to the bottom of the window.
Events at the top (almost) never crash when newly created.

[Snail]

See, this is a good policy that I usually follow, but when missions break the 400kb mark it starts taking 30s to several minutes just to close the events editor, so this becomes an incredible pain in the ass.

...

Won't be a problem for me then I guess.

[FUBAR-BDHR]

Unfortunately the only time I've had this happen I forgot to redo builds on that machine so I couldn't trace it.  It was a very simple test mission and happened after I deleted an event (possible the first one added) then right clicked on another.  I was unable to reproduce it though. 

[headdie]

In this case are we looking at an error in how FRED handles new / altered events prior to the program "saving" the changes to the temporary / mission file