Built Project Crash at rapidjson Call v1.8.1

Hi everyone,

we recently just compiled CesiumForUnreal v1.8.1 to work with. However, it is resulting in a crash ONLY in built projects.

The error only occurs when a World Terrain Tileset is present in the scene and the log indicates it is crashing during a rapidjson call.

We test multiple projects all were correctly work/still correctly work with the previous v1.7.0 release.

The project runs correctly in PIE and in Standalone but crash at startup of the built package.

Has anyone had this happen or suggest a workaround? For now we have rolled back to v1.7.0

[2021.12.09-05.03.23:103][  2]LogWindows: Could not start crash report client using ../../../Engine/Binaries/Win64/CrashReportClient-Win64-Debug.exe
[2021.12.09-05.03.23:103][  2]LogWindows: Error: Fatal error!
[2021.12.09-05.03.23:103][  2]LogMemory: Platform Memory Stats for WindowsNoEditor
[2021.12.09-05.03.23:103][  2]LogWindows: Error: 
[2021.12.09-05.03.23:103][  2]LogMemory: Process Physical Memory: 487.20 MB used, 531.70 MB peak
[2021.12.09-05.03.23:103][  2]LogMemory: Process Virtual Memory: 1145.21 MB used, 1145.96 MB peak
[2021.12.09-05.03.23:103][  2]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000010008
[2021.12.09-05.03.23:103][  2]LogMemory: Physical Memory: 33849.51 MB used,  97058.42 MB free, 130907.94 MB total
[2021.12.09-05.03.23:103][  2]LogWindows: Error: 
[2021.12.09-05.03.23:103][  2]LogMemory: Virtual Memory: 134047768.00 MB used,  169958.80 MB free, 134217728.00 MB total
[2021.12.09-05.03.23:103][  2]LogWindows: Error: [Callstack] 0x00007ff6d1a7e84b A1454_Wandoan_V3.exe!rapidjson::MemoryPoolAllocator<rapidjson::CrtAllocator>::Malloc() [D:\temp\UE4Source\ue427\Engine\Plugins\Custom\Sparky\Source\SparkyCommon\Private\rapidjson\allocators.h:181]
[2021.12.09-05.03.23:103][  2]Message dialog closed, result: Ok, title: The UE4-A1454_Wandoan_V3 Game has crashed and will close, text: Fatal error!


[2021.12.09-05.03.23:103][  2]LogWindows: Error: 
[2021.12.09-05.03.23:103][  2]LogThreadingWindows: Error: Runnable thread TaskGraphThreadNP 0 crashed.
[2021.12.09-05.03.23:103][  2]LogWindows: Error: Crash in runnable thread TaskGraphThreadNP 0

Hi @V2i,

Unfortunately, I’m not able to replicate this on my end, but it definitely sounds Cesium-related if it’s only happening when CWT is in the level.
I noticed the line [2021.12.09-05.03.23:103][ 2]LogWindows: Error: [Callstack] 0x00007ff6d1a7e84b A1454_Wandoan_V3.exe!rapidjson::MemoryPoolAllocator<rapidjson::CrtAllocator>::Malloc() [D:\temp\UE4Source\ue427\Engine\Plugins\Custom\Sparky\Source\SparkyCommon\Private\rapidjson\allocators.h:181] in your error log. Is this Sparky plugin used in all of your projects? Are you able to disable it and see if that allows you to run a built project?

If it’s possible that this other plugin is contributing to this issue, it could be helpful to know more about that plugin to figure out if there’s anything we can adjust in the Cesium plugin code to prevent other issues like this.

-Alex

Hi @agallegos ,

We managed to resolve this on our own. The Cesium For Unreal rapidjson call were also calling the rapidjson functions we have in our own Sparky plugin for some reason even though they are separate. We just refactored our implementation and it’s resolved.

1 Like