[4.7.0] When an event on a component called from an actor's constructor is deleted, the editor crashes hard

I ‘accidentally’ deleted an event on an attached component that was called by an actor’s constructor, and the editor crashed hard.

I’ve also had some other minor bugs that I believe are caused by the way the components handle circular references, where a level containing an actor attached to a component refuses to save because the component is a ‘private object’.

Hey drekmonger,

With the information given, I’m not able to reproduce this crash. Could you give me more detailed steps for recreating this crash - either a picture of your blueprint setup or the code you used?

Here’s an imgur album with screenshots of the problem: Drek's Bug Report, Unreal - Album on Imgur

When Foo is deleted from the NewActorComponent and the BP compiled, the editor hangs for about 30 seconds, then crashes. I just tested this in 4.7.2, and the problem still exists.

I realize this isn’t going to be a problem that very many people encounter, but since it’s a crash, I figured y’all would want to know about it. Thanks for your time!

I’m not experiencing any crash when following those steps:

Is there something I’m doing incorrectly?

Hello drekmonger,

We have not heard back from you in a few days… If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance. I tried reproducing this issue with the information above and was unsuccessful. I have a couple of questions for you.

Quick questions:

  1. Can you reproduce this issue in a clean project?
  2. If so, could provide a detailed list of steps to reproduce this issue on our end?

Thank you.

Sorry for the delay. I haven’t been paying attention, to be honest.

I was able to duplicate the bug again, following the steps in Jonathan Dorman’s screenshot, in a blank project. I’m still running 4.7.2. Also, my operating system is Windows 10 (the tech preview). It could be that, or some other machine specific issue, causing the bug if you aren’t able to duplicate.

(Aside from a pair of laptops that are insufficient for running Unreal, I don’t have another machine on hand to test.) Sorry again for the delay; I’m presently assuming there’s some weirdness on my machine, perhaps Win10, causing the crash.

The crash report’s text has been attached in a txt file:
link text

Hello drekmonger,

It is possible that it could be a windows 10 issue due to the fact that windows 10 is not officially supported yet. However, I would like like to try and rule this out. Would it be possible for you to send me your project that is having the issue? This way I will be able to test in on our end and possibly rule out that factor.

I’ve created a new project each time. I’ve just built a new one and uploaded it to dropbox: Dropbox - Error - Simplify your life

The short story: To duplicate the crash, drag DoomedActor into the level, then delete the event doStuff from DoomedComponent.

The longer story: While making this new project, a detail I overlooked in my previous reports occurred to me. The actor containing the component has an instance on the stage. That may be the missing ingredient for duplicating the crash. I just confirmed: deleting the event does not crash the editor, so long as the actor is not on the stage.

When I tried to save the map containing an instance of the actor, an error message pops up:

Can’t save
…/…/…/…/…/…/Users/drek/Documents/Unreal
Projects/drek_bugtest/Content/Untitled.umap:
Graph is linked to private object(s)
in an external package. External
Object(s): DoomedComponent_0 Try to
find the chain of references to that
object (may take some time)?

And then:

The asset ‘/Game/Untitled’
(Untitled.umap) failed to save.

Cancel: Stop saving all assets and
return to the editor. Retry: Attempt
to save the asset again. Continue:
Skip saving this asset only.

| remember encountering this before. Should have included the detail in the bug report.

Replied below. Just making sure you get a notification, since I failed to directly reply to your message.

Thanks to everyone for all your time, again.

Hello drekmonger,

I was able to reproduce the crash on my end. I have written up a report (UE-11941) and I have submitted it to the developers for further consideration. I will provide updates with any pertinent information as it becomes available. Thank you for you time and information.

Make it a great day