# Crash while calling parent blueprint in the cooked game 

**URL:** <https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420>\
**Category:** Platform & Builds\
**Tags:** unreal-engine, Epic-Pro-Support, question\
**Created:** [April 20, 2026, 3:18pm UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420 "2026-04-20T15:18:15Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [April 20, 2026, 3:18pm UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/1 "2026-04-20T15:18:15Z")

</div>

I had an issue with the game crashing in the cooked game inside of a blueprint code. I have a BP\_Parent and BP\_Child with the function HandleDeath. The child overrides the parent function and once the child calls the parent method it crashes.

Observations:

- It crashes even though the parent HandleDeath function is empty.
- The crashes stopped occuring after I disconnect the Parent:HandleDeath node

I made some debugging and found out that FindFunction returns the SKEL\_\* blueprint in GetMostUpToDateClass. So I’ve tried the following change and it seems to resolve the issue.

[Image Removed]

Did you encounter a similar issue? What do you think of this change (see screenshot)? Is this fix legitimate?

EDIT: It seem to fix a similar PIE issue, so it’s not limited to only cooked game.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [April 20, 2026, 3:18pm UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/2 "2026-04-20T15:18:19Z")

</div>

**Steps to Reproduce**  
These steps are approximate:

- Make BP\_Parent with function HandleDeath
- Derive a BP\_Child
- Override HandleDeath and add Parent:HandleDeath node
- Cook the game
- There is a c++ delegate which call the HandleDeath method od the child BP
- Crash

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![ZhiKangShao](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/zhikangshao/32/1089997_2.png) [@ZhiKangShao](https://forums.unrealengine.com/u/ZhiKangShao)\
**Post date:** [April 30, 2026, 4:32pm UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/3 "2026-04-30T16:32:35Z")

</div>

Hello! Although I’m glad to hear that that modification unblocks you, the crash you’re experiencing shouldn’t be solved in a CallParentFunction specific way.

I tried out the repro steps you provided but this doesn’t crash on my end. We’ll need more info and a way to reproduce the crash at will to investigate an engine fix. Can you reproduce it at will?

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![ZhiKangShao](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/zhikangshao/32/1089997_2.png) [@ZhiKangShao](https://forums.unrealengine.com/u/ZhiKangShao)\
**Post date:** [April 30, 2026, 5:34pm UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/4 "2026-04-30T17:34:28Z")

</div>

A few questions we have that might be relevant. Looking at your callstack:

- What is the name of the C++ delegate?
- Which object has the HandleDeath function, is that the component that also has the delegate or is it a different object?
- Is HandleDeath a blueprint declared function, or native declared and blueprint overridden? (BlueprintNativeEvent)
- How do you bind HandleDeath to that delegate?  
[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [May 11, 2026, 11:09am UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/5 "2026-05-11T11:09:27Z")

</div>

Hi, sorry for late reply.

Yes, I’m able to reproduce it on our code base.

- Its the OnCharacterDeath delegate on an actor component (UWhCombatActorComponent)

```auto
DECLARE_DYNAMIC_MULTICAST_DELEGATE_OneParam(FOnCharacterDeathDynamic, AActor*, Actor);
//...
UPROPERTY(BlueprintAssignable)
FOnCharacterDeathDynamic OnCharacterDeath;

```

- The HandleDeath is on a different object, its the AC\_Switch\_Enemy component (created in BP). The BP class hierarchy is ActorComponent \> AC\_Switch \> AC\_Switch\_Enemy. Both of the components share the same owner.
- The HandleDeath function is declared on AC\_Switch and overriden in AC\_Switch\_Enemy
- The binding is done via CreateEvent node. As an experiment I’ve tried to bind it via CustomEvent which then called HandleDeath, but the result was the same.

Does that answer all the questions?

Thank you for you time. If any question arise, I will try to answer them asap.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![ZhiKangShao](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/zhikangshao/32/1089997_2.png) [@ZhiKangShao](https://forums.unrealengine.com/u/ZhiKangShao)\
**Post date:** [May 11, 2026, 3:40pm UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/6 "2026-05-11T15:40:13Z")

</div>

Thank you, that info is quite helpful to point the picture. I need a few more details:

- Is AC\_Switch\_Enemy a default subobject of the character actor (AMyCharacter creates it via CreateDefaultSubobject in actor constructor) or is it a SimpleConstructionScript component (BP\_MyCharacter adds the component in the component tree)
- How about UWhCombatActorComponent?
- Who binds AC\_Switch\_Enemy’s HandleDeath function to UWhCombatActorComponent’s OnCharacterDeath, is it
  - (a) AC\_Switch\_Enemy it self via a reference to the WhCombatActorComp?
  - (b) Or is it the actor that owns both AC\_Switch and the WhCAC?

Some workarounds I’d like you to try:

- If you’re currently doing the binding directly via event nodes (details panel of a component reference \> Events), I’d like you to try is whether binding the event explicitly on BeginPlay. I mean: on BeginPlay, resolve the WhCAC and call [Bind Event to OnCharacterDeath] or [Assign to OnCharacterDeath] in blueprint.
  - Directly binding via UK2Node\_ComponentBoundEvent has historically had some bugs specific to that method of binding.

- Recreate the [Parent: Handle Death] nodes by right clicking on the entry node of AC\_Switch\_Enemy’s Handle Death function graph \> Add Call to Parent Function.
  - What this is meant to rule out is maybe a parent function call node got copied from a sibling blueprint.  
[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [May 12, 2026, 10:57am UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/7 "2026-05-12T10:57:27Z")

</div>

I checked the structure once again and I was wrong about one thing.

- The AC\_Switch\_Enemy is not a component of the actor, but its controller. The Actor has AIController which owns the AC\_Switch\_Enemy component.

To answer your questions:

- 1) The AC\_Switch\_Enemy (child) is added in the component tree (So SimpleConstructionScript it is).
- 2) UWhCombatActorComponent is created via CreateDefaultSubobject.
- 3) In the AC\_Switch (the parent class) in event graph there is OnPossessedPawnChanged delegate. If the delegate is fired I get a reference to the UWhCombatActorComponent by GetComponentByClass and connect it in this manner: [Image Removed] [Image Removed]
- Now that I’m writting it, isn’t the problem that the base class is creating the binding?

About the workarounds:

- If I understand it correctly, you are suggesting bind the event directly on BeginPlay. That does not work for me because that is too soon and UWhCAC is not initialized (?). But I think it is similar what you are suggesting but using a diffrent signal (screenshot above).
- I’ve tried recreating the “add call to parent function” in the past and it did not change anything.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![ZhiKangShao](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/zhikangshao/32/1089997_2.png) [@ZhiKangShao](https://forums.unrealengine.com/u/ZhiKangShao)\
**Post date:** [May 14, 2026, 11:34am UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/8 "2026-05-14T11:34:43Z")

</div>

Thank you. I’ve used the information to try and reproduce your exact setup, but still can’t get the crash to happen. This all is helpful through to converge on what condition is diverging from expectation.

My preference would be to continue comparing until we find out what situation causes the repro, before accepting an engine change that might just conceal a bigger problem. I’ll ask for more info, but I also understand that if at some point you would prefer to just keep your fix/workaround and leave it at that from your side.

The two questions I have currently are:

- Is there a dependency from parent BP to child BP? I.e. is AC\_Switch\_Enemy compiled _while_ AC\_Switch is still compiling? Our expectation is that AC\_Switch, since its the base class, has finished compiling by the time AC\_Switch\_Enemy is being compiled so the function here should resolve to the non-skeleton blueprint generated class. You might find a cyclical dependency via [my steps here](https://dev.epicgames.com/community/learning/knowledge-base/oEn6/guide-investigating-blueprint-data-loss-issues-in-unreal-engine#recognizingcyclicaldependencies).
- Which of the conditions is causing that CallingContext = FBlueprintEditorUtils::GetMostUpToDateClass to be entered here when compiling HandleDeath and the CallParentFunction node in it? I.e. which of the 3 OR conditions is true?

One theoretical scenario where I imagine this issue might happen, is if the child BP (AC\_Switch\_Enemy) is compiled before its parent (AC\_Switch) has finished compiling, which can explain why compilation of AC\_Switch\_Enemy:HandleDeath accesses a skeleton BP.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [May 22, 2026, 10:20am UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/9 "2026-05-22T10:20:05Z")

</div>

Sorry, my focus was something else these few days. I’m motivated to help you figure it out, so that’s not a problem.

To answer your questions:

1) I didn’t find any circular dependecy between the child and parent blueprint, but there might be a cycle formed by AC\_Switch by itself.

[Image Removed]There is this AC\_NPCGroup which uses the AC\_Switch in this manner.

[Image Removed]I didn’t run any further tests as you mention in the linked article, since the class is not a c++ class, but a blueprint (I wouldn’t know where to put the breakpoint). Do you think it would be useful to elaborate more?

2) It was the 3rd condition.

To add more details I can you the whole print. I’ve added this test print:

[Image Removed]Somehow its was called multiple times. The results is

```auto
LogK2Compiler: Warning: [COMPILE DEBUG] FindFunction for PARENT CALL | FunctionName: HandleDeath | CallingContextBeforeRedirect: AC_Switch_C | CallingContext (after redirect/skip): SKEL_AC_Switch_C | WasRedirected: YES | BlueprintContext: AC_Switch (bBeingCompiled: false, IsUpToDate: false) | FoundFunction: Function /Game/Blueprints/Components/AC_Switch.SKEL_AC_Switch_C:HandleDeath (ptr: 0x0000025A2EDA7BC0) | CondA: 0 | CondB: 0 = 0 & 1 | CondC: 1 = 1 & 1
LogK2Compiler: Warning: [COMPILE DEBUG] FindFunction for PARENT CALL | FunctionName: HandleDeath | CallingContextBeforeRedirect: AC_Switch_C | CallingContext (after redirect/skip): SKEL_AC_Switch_C | WasRedirected: YES | BlueprintContext: AC_Switch (bBeingCompiled: false, IsUpToDate: false) | FoundFunction: Function /Game/Blueprints/Components/AC_Switch.SKEL_AC_Switch_C:HandleDeath (ptr: 0x0000025A2EDA7BC0) | CondA: 0 | CondB: 0 = 0 & 0 | CondC: 1 = 1 & 1
LogK2Compiler: Warning: [COMPILE DEBUG] FindFunction for PARENT CALL | FunctionName: HandleDeath | CallingContextBeforeRedirect: AC_Switch_C | CallingContext (after redirect/skip): SKEL_AC_Switch_C | WasRedirected: YES | BlueprintContext: AC_Switch (bBeingCompiled: false, IsUpToDate: false) | FoundFunction: Function /Game/Blueprints/Components/AC_Switch.SKEL_AC_Switch_C:HandleDeath (ptr: 0x0000025A2EDA7BC0) | CondA: 0 | CondB: 0 = 0 & 0 | CondC: 1 = 1 & 1

```

If you need anymore info, let me know.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![ZhiKangShao](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/zhikangshao/32/1089997_2.png) [@ZhiKangShao](https://forums.unrealengine.com/u/ZhiKangShao)\
**Post date:** [June 12, 2026, 11:30am UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/10 "2026-06-12T11:30:05Z")

</div>

Thanks for those debug logs. That’s very helpful! And thanks for your patience. It took me a while to circle back because I was OOO.

**!bBeingCompiled** and **!IsUpToDate()** is an unexpected combination, because if the parent blueprint wasn’t up to date, it should have been flagged for compilation in GatherOutOfDateDependenciesRecursive. Can you print out what the value of **BlueprintContext-\>Status** is? I think that will provide the next hint.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [June 25, 2026, 9:18pm UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/11 "2026-06-25T21:18:18Z")

</div>

No worries, I was also out of office so it took me some time.

It shows BlueprintContext-\>Status == 1 (BS\_Dirty), while most of the other blueprint in the log have 3 (BS\_UpToDate)

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![ZhiKangShao](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/zhikangshao/32/1089997_2.png) [@ZhiKangShao](https://forums.unrealengine.com/u/ZhiKangShao)\
**Post date:** [June 26, 2026, 10:55pm UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/12 "2026-06-26T22:55:51Z")

</div>

That’s very good to know! I believe the parent blueprint having status BS\_Dirty while not being flagged for compilation (!bIsBeingCompiled) is the unexpected combination and that might be the problem to investigate further.

I’m passing this case on to my coworker who is more familiar with that part of the BP compiler. Epic is having a company-wide two week break, so we’ll continue investigating on July 6th.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![DanIsNeat](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@DanIsNeat](https://forums.unrealengine.com/u/DanIsNeat)\
**Post date:** [June 27, 2026, 1:34am UTC](https://forums.unrealengine.com/t/crash-while-calling-parent-blueprint-in-the-cooked-game/2738420/13 "2026-06-27T01:34:13Z")

</div>

Wanted to leave a quick note before I went on break:

1. Consider using disasmscript \<classname\> to compare the problematic call to a basic parent function invocation
2. This workaround should be safe, a test case will speed up integration of the fix on our end  
[Attachment Removed]
