[4.6.1] Crashes on project load due to event dispatcher

Heyhey,

I’ve managed to bork my project in some way using event dispatchers. I can no longer open my project, instead getting an access violation error (here’s log).

Looking at it, it seems like using event dispatchers was a problem. Unfortunately, 15 minutes of tinkering in a sandbox hasn’t let me recreate this, and instead I’ve just rolled back my blueprint.

For a little more context, what I’d been doing is spawning an actor in Event Begin Play which had a lot of custom event dispatchers (only one with an input parameter which was of a custom blueprint class type), then hooking up these to custom events in my owning blueprint.

Hopefully there’s enough information here to help you guys find problem - if not, let me know what I can do. For now, I think I have to ignore this and hope it’ll get fixed for 4.7.0.

This BUG already have ticket on Epic…see link below:

Event Dispatcher 4.6.1

Ah, I had seen that, but is that not specifically to do with GameMode BP? I’m using BPs that descend from actor, so either this is a different bug or bug is broader than initially reported.

Seems to me problem is EventDispatcher itself. But, in 7.2 Preview, fix has already done. DO you try to test in 7.2 preview with same conditions?

Hey MkII,

I believe issue you’re facing is related to one reported here:

However, I don’t believe bug (which involved Event Dispatchers not being called in Standalone Game or cooked builds) was causing a crash. Can you try opening project in 4.7 Preview and seeing if it will open? Thanks!

Hey ,

I’ve tried to upgrade a copy of my project to 4.7 preview, but unfortunately I run across this problem, so I can’t recreate setup that crashes 4.6.1 in 4.7.

I might try making BP from scratch quickly with copy pasta and seeing if I can get anywhere with that.

As I replied to above, I’m having problems with 4.7 preview 3. If I do manage to recreate setup in 4.7 I’ll report back.

And I keep running into more and more problems, with casting, with event dispatcher, all for this one blueprint. I don’t think I can recreate this in 4.7 since every step I manage to make towards it ends up crashing editor (and original issue has editor working fine, just crashing on load).

Okay, well, looking at crash log you initially posted, it seems to be crashing after it fails to find a parent component, ‘NodeSprite’:

[2015.01.13-13.03.54:699][  0]LogBlueprint:Warning: USimpleConstructionScript::FixupRootNodeParentReferences() - Couldn't find inherited parent component 'NodeSprite' for 'ProduceSprite' in BlueprintGeneratedClass 'REINST_BP_Node_Produce_C_160' (it may have been removed)

Is it possible that something was deleted and you’re still referencing it somewhere?

I don’t believe so. In my rolled back project that doesn’t crash, I get that warning in logs too.

I tried to get back into crashing case, step by step, closing down editor and reopening it after adding each small part of logic. When I got to binding to a second event, everything seemed fine and I could close and open my project, but this time when I hit compile (after reopening project), UE4 stops responding and standard Windows ‘process has stopped working’ message appeared - no UE4 editor crash report (so a different bug perhaps).

:

In this second case, removing new step and going back to previous case still resulted in a crash, which is just confusing!

Is it same crash? Can you attach log for me?

It’s not same as first crash, no, because first crash came up with UE crash report box, and occurred on project startup, as opposed to this one, which occurs on compile and displays no UE crash report. log is here

I can understand if two are related though, since first crash occurred when I put more ‘bind event to’ nodes in (3 more I think) and reopened my project next day, whereas this crash happens with fewer nodes, but requires project to be reopened.

Do you think this requires a separate bug report?

No, I think it’s all rooted in Event Dispatcher. We have another bug report open already for Event Dispatcher causing a particular crash, but it looks like you’re getting something different so I’d like to keep investigating it here for now. It’s possible that fixing one will fix other as well.

It looks like this second log you attached is truncated. Can you grab tagged with time of crash? Thanks!

Yep, trying it again (in a cloned project since original is moving on) log is indeed truncated. I assume you mean a screen grab with time showing?

[Corresponding log][2]

If it would help, I can upload whole project somewhere for you guys - it’s only 350MB and all assets are programmer art or ripped from web. Let me know where I can put it if you do want it!

That may be helpful, thanks. You can upload it to a Dropbox account and leave a link here for me to download it from. Thanks!

First time I’m doing this, but hopefully it should all be fine:

Edit: Link removed - potentially unsafe :frowning:

My system doesn’t like that download, says it contains something malicious.

That’s not good. I’ll take down link and do a virus scan - what software gave you warning? I’m using freebie Avira and not had anything crop up, but maybe that’s just because it’s crap.

Not good at all. I ran an AV against my local copy, and nothing turned up. I’m using free Avira - can I ask what program gave you warning?

I’m hoping it’s just a false positive to do with packaged .exe in saved folder but I would like to be sure!

It was Chrome, actually, it never got to my av. Put it up again and I’ll see if it gives me more trouble than that.