# FStaticMeshInstanceBuffer Crash on PIE

**URL:** <https://forums.unrealengine.com/t/fstaticmeshinstancebuffer-crash-on-pie/401896>\
**Category:** Asset Creation\
**Tags:** buffer, UE4-17, instance, unreal-engine, bug-report, question\
**Created:** [August 12, 2017, 10:36pm UTC](https://forums.unrealengine.com/t/fstaticmeshinstancebuffer-crash-on-pie/401896 "2017-08-12T22:36:16Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous\_user\_416b781b](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_416b781b](https://forums.unrealengine.com/u/anonymous_user_416b781b)\
**Post date:** [August 12, 2017, 10:36pm UTC](https://forums.unrealengine.com/t/fstaticmeshinstancebuffer-crash-on-pie/401896/1 "2017-08-12T22:36:16Z")

</div>

I updated from UE 4.16.1 to UE 4.17.

Often, when I try to start playing in the editor, I get a crash regarding the FStaticMeshInstanceBuffer. This is the Crash report:

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

UE4Editor\_Engine!FStaticMeshInstanceBuffer::UpdateInstanceData() [d:\build++ue4+release-4.17+compile\sync\engine\source\runtime\engine\private\instancedstaticmesh.cpp:137]  
UE4Editor\_Engine!FPerInstanceRenderData::UpdateInstanceData() [d:\build++ue4+release-4.17+compile\sync\engine\source\runtime\engine\private\instancedstaticmesh.h:431]  
UE4Editor\_Engine!UInstancedStaticMeshComponent::PostDuplicate() [d:\build++ue4+release-4.17+compile\sync\engine\source\runtime\engine\private\instancedstaticmesh.cpp:2052]  
UE4Editor\_CoreUObject!StaticDuplicateObjectEx() [d:\build++ue4+release-4.17+compile\sync\engine\source\runtime\coreuobject\private\uobject\uobjectglobals.cpp:2060]  
UE4Editor\_CoreUObject!StaticDuplicateObject() [d:\build++ue4+release-4.17+compile\sync\engine\source\runtime\coreuobject\private\uobject\uobjectglobals.cpp:1917]  
UE4Editor\_UnrealEd!UEditorEngine::CreatePIEWorldByDuplication() [d:\build++ue4+release-4.17+compile\sync\engine\source\editor\unrealed\private\playlevel.cpp:3847]  
UE4Editor\_Engine!UGameInstance::InitializeForPlayInEditor() [d:\build++ue4+release-4.17+compile\sync\engine\source\runtime\engine\private\gameinstance.cpp:200]  
UE4Editor\_UnrealEd!UEditorEngine::CreatePIEGameInstance() [d:\build++ue4+release-4.17+compile\sync\engine\source\editor\unrealed\private\playlevel.cpp:3069]  
UE4Editor\_UnrealEd!UEditorEngine::PlayInEditor() [d:\build++ue4+release-4.17+compile\sync\engine\source\editor\unrealed\private\playlevel.cpp:2526]  
UE4Editor\_UnrealEd!UEditorEngine::StartQueuedPlayMapRequest() [d:\build++ue4+release-4.17+compile\sync\engine\source\editor\unrealed\private\playlevel.cpp:1218]  
UE4Editor\_UnrealEd!UEditorEngine::Tick() [d:\build++ue4+release-4.17+compile\sync\engine\source\editor\unrealed\private\editorengine.cpp:1549]  
UE4Editor\_UnrealEd!UUnrealEdEngine::Tick() [d:\build++ue4+release-4.17+compile\sync\engine\source\editor\unrealed\private\unrealedengine.cpp:396]  
UE4Editor!FEngineLoop::Tick() [d:\build++ue4+release-4.17+compile\sync\engine\source\runtime\launch\private\launchengineloop.cpp:3215]  
UE4Editor!GuardedMain() [d:\build++ue4+release-4.17+compile\sync\engine\source\runtime\launch\private\launch.cpp:166]  
UE4Editor!GuardedMainWrapper() [d:\build++ue4+release-4.17+compile\sync\engine\source\runtime\launch\private\windows\launchwindows.cpp:134]  
UE4Editor!WinMain() [d:\build++ue4+release-4.17+compile\sync\engine\source\runtime\launch\private\windows\launchwindows.cpp:210]  
UE4Editor!\_\_scrt\_common\_main\_seh() [f:\dd\vctools\crt\vcstartup\src\startup\exe\_common.inl:253]  
kernel32  
ntdll

After updating my project the error occured everytime I started PIE. Then I deleted all my blueprints which used a instance static mesh component and the error vanished.

Edit: I can confirm, when no instanced static mesh components are used this crash does not occcur.

---

<div class="post-metadata">

**Author:** ![fxs\_don](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@fxs\_don](https://forums.unrealengine.com/u/fxs_don)\
**Post date:** [August 17, 2017, 2:33pm UTC](https://forums.unrealengine.com/t/fstaticmeshinstancebuffer-crash-on-pie/401896/2 "2017-08-17T14:33:57Z")

</div>

I ran into this issue as well.

In FStaticMeshInstanceBuffer::SetupCPUAccess(), the function tries to get the CVar value by calling CVar-\>GetValueOnGameThread(). Since nearly everything is Async Loading now, and this call can happen on the loading thread, you get the crash since it ensures that the call can only be made on the game thread.

So, you can do one of two things:

1. Don’t Async load anything.

2. Change the call to CVar-\>GetValueOnAnyThread().

I made the second change in my codebase without any issue.

Hope that helps!

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_416b781b](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_416b781b](https://forums.unrealengine.com/u/anonymous_user_416b781b)\
**Post date:** [August 19, 2017, 7:18pm UTC](https://forums.unrealengine.com/t/fstaticmeshinstancebuffer-crash-on-pie/401896/3 "2017-08-19T19:18:59Z")

</div>

Hey fxs\_don,

thank you for your reply, glad you found a fix. At the moment I’m using the launcher version so I can’t apply your fix. I hope this gets some attention from Epic. Maybe you would be able to provide them a commit with the fix?

---

<div class="post-metadata">

**Author:** ![poke1103](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@poke1103](https://forums.unrealengine.com/u/poke1103)\
**Post date:** [September 3, 2017, 5:24am UTC](https://forums.unrealengine.com/t/fstaticmeshinstancebuffer-crash-on-pie/401896/4 "2017-09-03T05:24:38Z")

</div>

I have this same issue, I will test this fix, I hope it works 😉

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_565e242f](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_565e242f](https://forums.unrealengine.com/u/anonymous_user_565e242f)\
**Post date:** [September 18, 2017, 5:01pm UTC](https://forums.unrealengine.com/t/fstaticmeshinstancebuffer-crash-on-pie/401896/5 "2017-09-18T17:01:18Z")

</div>

Hi

A fix was made for 4.17.2 that should be release quite soon.

---

<div class="post-metadata">

**Author:** ![poke1103](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@poke1103](https://forums.unrealengine.com/u/poke1103)\
**Post date:** [September 18, 2017, 5:15pm UTC](https://forums.unrealengine.com/t/fstaticmeshinstancebuffer-crash-on-pie/401896/6 "2017-09-18T17:15:07Z")

</div>

Is there a release date set?

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_565e242f](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_565e242f](https://forums.unrealengine.com/u/anonymous_user_565e242f)\
**Post date:** [September 18, 2017, 5:16pm UTC](https://forums.unrealengine.com/t/fstaticmeshinstancebuffer-crash-on-pie/401896/7 "2017-09-18T17:16:09Z")

</div>

When QA approved it 🙂

---

<div class="post-metadata">

**Author:** ![poke1103](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@poke1103](https://forums.unrealengine.com/u/poke1103)\
**Post date:** [September 18, 2017, 5:18pm UTC](https://forums.unrealengine.com/t/fstaticmeshinstancebuffer-crash-on-pie/401896/8 "2017-09-18T17:18:05Z")

</div>

Alright, cool. 🙂

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_416b781b](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_416b781b](https://forums.unrealengine.com/u/anonymous_user_416b781b)\
**Post date:** [September 19, 2017, 3:56pm UTC](https://forums.unrealengine.com/t/fstaticmeshinstancebuffer-crash-on-pie/401896/9 "2017-09-19T15:56:41Z")

</div>

Thank you, Mr. Dupuis, for the reply, I’m glad this issue is fixed soon.
