Description

Error Message: Access violation - code c0000005 (first/second chance not available)

ComponentOverlapComponent node used in blueprints will cause the editor to crash once you PIE if there is no component connected to the blue component pin on the ComponentOverlapComponents node.

Steps to Reproduce

1. Create a new blueprint template
2. Create a new actor blueprint
3. Create a blueprint setup like the attached picture or project zip

Callstack

UE4Editor_Engine!UKismetSystemLibrary::ComponentOverlapComponents_NEW() [kismetsystemlibrary.cpp:1149]
UE4Editor_Engine!UKismetSystemLibrary::execComponentOverlapComponents_NEW() [kismetsystemlibrary.h:61]
UE4Editor_CoreUObject!UFunction::Invoke() [class.cpp:4125]
UE4Editor_CoreUObject!UObject::CallFunction() [scriptcore.cpp:463]
UE4Editor_CoreUObject!UObject::ProcessContextOpcode() [scriptcore.cpp:1552]
UE4Editor_CoreUObject!UObject::execLetBool() [scriptcore.cpp:1469]
UE4Editor_CoreUObject!UObject::ProcessInternal() [scriptcore.cpp:673]
UE4Editor_CoreUObject!UFunction::Invoke() [class.cpp:4125]
UE4Editor_CoreUObject!UObject::ProcessEvent() [scriptcore.cpp:1023]
UE4Editor_Engine!AActor::ProcessEvent() [actor.cpp:520]
UE4Editor_Engine!FLatentActionManager::TickLatentActionForObject() [latentactionmanager.cpp:169]
UE4Editor_Engine!FLatentActionManager::ProcessLatentActions() [latentactionmanager.cpp:99]
UE4Editor_Engine!UWorld::Tick() [leveltick.cpp:1218]
UE4Editor_UnrealEd!UEditorEngine::Tick() [editorengine.cpp:1339]
UE4Editor_UnrealEd!UUnrealEdEngine::Tick() [unrealedengine.cpp:366]
UE4Editor!FEngineLoop::Tick() [launchengineloop.cpp:2359]
UE4Editor!GuardedMain() [launch.cpp:142]
UE4Editor!GuardedMainWrapper() [launchwindows.cpp:126]
UE4Editor!WinMain() [launchwindows.cpp:200]

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-18936 in the post.

0
Login to Vote

Fixed
ComponentUE - Gameplay
Affects Versions4.8
Target Fix4.9
Fix Commit2628826
Release Commit2636852
CreatedJul 21, 2015
ResolvedJul 22, 2015
UpdatedApr 27, 2018
View Jira Issue