Unhandled Exception: EXCEPTION_ACCESS_VIOLATION removeCollisionForTiles(pResult->tilesFadingOut);

Alessio_Masola · March 31, 2025, 4:22pm

Hello there!
I’m currently Using Unreal Engine v 5.3.2 (cesium 5.3.0 by marketplace)

after two hour of execution i get this error at this line:

Cesium3DTileset.cpp:2056

that should be this line of code: removeCollisionForTiles(pResult->tilesFadingOut);
https://github.com/CesiumGS/cesium-unreal/blob/main/Source/CesiumRuntime/Private/Cesium3DTileset.cpp

[2025.03.31-15.40.20:752][679]LogWindows: Could not start crash report client using ../../../Engine/Binaries/Win64/CrashReportClient-Win64-Debug.exe
[2025.03.31-15.40.20:753][679]LogMemory: Platform Memory Stats for Windows
[2025.03.31-15.40.20:753][679]LogMemory: Process Physical Memory: 1117.50 MB used, 1177.82 MB peak
[2025.03.31-15.40.20:753][679]LogMemory: Process Virtual Memory: 3534.59 MB used, 3643.85 MB peak
[2025.03.31-15.40.20:753][679]LogMemory: Physical Memory: 27411.89 MB used,  21361.65 MB free, 48773.54 MB total
[2025.03.31-15.40.20:753][679]LogMemory: Virtual Memory: 38281.09 MB used,  58492.45 MB free, 96773.54 MB total
[2025.03.31-15.40.20:753][679]Message dialog closed, result: Ok, title: The UE-Masa Game has crashed and will close, text: Fatal error!


[2025.03.31-15.40.20:753][679]LogWindows: Error: === Critical error: ===
[2025.03.31-15.40.20:753][679]LogWindows: Error: 
[2025.03.31-15.40.20:753][679]LogWindows: Error: Fatal error!
[2025.03.31-15.40.20:753][679]LogWindows: Error: 
[2025.03.31-15.40.20:753][679]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000019f5e77a7d8
[2025.03.31-15.40.20:753][679]LogWindows: Error: 
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e732a230 Masa-Win64-DebugGame.exe!Cesium3DTilesSelection::Tile::getState() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e3521174 Masa-Win64-DebugGame.exe!ACesium3DTileset::Tick() [D:\build\U5M\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\CesiumForUnreal\Source\CesiumRuntime\Private\Cesium3DTileset.cpp:2056]
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e157b48c Masa-Win64-DebugGame.exe!AActor::TickActor() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e155031c Masa-Win64-DebugGame.exe!FActorTickFunction::ExecuteTick() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e2bdf43f Masa-Win64-DebugGame.exe!FTickFunctionTask::DoTask() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e2be5887 Masa-Win64-DebugGame.exe!TGraphTask<FTickFunctionTask>::ExecuteTask() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6dc074c97 Masa-Win64-DebugGame.exe!FNamedTaskThread::ProcessTasksNamedThread() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6dc07528e Masa-Win64-DebugGame.exe!FNamedTaskThread::ProcessTasksUntilQuit() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6dc07ff3d Masa-Win64-DebugGame.exe!FTaskGraphCompatibilityImplementation::WaitUntilTasksComplete() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e2bf93ae Masa-Win64-DebugGame.exe!FTickTaskSequencer::ReleaseTickGroup() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e2bff154 Masa-Win64-DebugGame.exe!FTickTaskManager::RunTickGroup() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e21512e3 Masa-Win64-DebugGame.exe!UWorld::Tick() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e1eb6fe1 Masa-Win64-DebugGame.exe!UGameEngine::Tick() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e34866b3 Masa-Win64-DebugGame.exe!FEngineLoop::Tick() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e349e3ec Masa-Win64-DebugGame.exe!GuardedMain() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e349e4ca Masa-Win64-DebugGame.exe!GuardedMainWrapper() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e34a1376 Masa-Win64-DebugGame.exe!LaunchWindowsStartup() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e34b0f74 Masa-Win64-DebugGame.exe!WinMain() []
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ff6e7b95d9a Masa-Win64-DebugGame.exe!__scrt_common_main_seh() [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288]
[2025.03.31-15.40.20:753][679]LogWindows: Error: [Callstack] 0x00007ffc9832259d KERNEL32.DLL!UnknownFunction []
[2025.03.31-15.40.20:753][679]LogWindows: Error: 
[2025.03.31-15.40.20:761][679]LogExit: Executing StaticShutdownAfterError
[2025.03.31-15.40.20:762][679]LogWindows: FPlatformMisc::RequestExit(1, LaunchWindowsStartup.ExceptionHandler)
[2025.03.31-15.40.20:762][679]LogWindows: FPlatformMisc::RequestExitWithStatus(1, 3, LaunchWindowsStartup.ExceptionHandler)
[2025.03.31-15.40.20:762][679]LogCore: Engine exit requested (reason: Win RequestExit)

i’ve got also this error two times after opening the application (shipped in debug mode as single executable)

Maybe it could be useful the crash:
UECC-Windows-8F60EFFB4E238446A9399884E3A9EFB4_0000.rar (67.4 KB)

The same error occurred three times.

The first occurrence happened during a pressure test involving the spawning of multiple actors with meshes. The error appeared after 2 hours of execution.
The other two occurrences happened upon opening the application, approximately 10 seconds after startup, without any user interactions or tests being performed.

thank you for your time,
Alessio

Kevin_Ring · April 3, 2025, 1:52am

Hi Alessio,
Can you please check your version of Cesium for Unreal. The Marketplace has a long-standing bug where it reports the Unreal Engine version as the plugin version. Instead, look in the lower-right corner of the Cesium panel in the Editor.

Alessio_Masola · April 3, 2025, 8:09am

Morning Kevin,
thank you for the fast reply!

The Cesium Version is 2.14.1

But the first day of april there still the version 2.15 but is not currently available from the marketplace,
right?

github.com/CesiumGS/cesium-unreal

CHANGES.md

main

# Change Log {#changes}

### v2.15.0 - 2025-04-01

##### Additions :tada:

- Actors spawned through the Cesium editor panel, such as tilesets and cartographic polygons, will now be parented to the first selected georeference - if any - instead of always being parented to the first georeference in the scene.
- `WorldHeight` Runtime Virtual Texture output is now set to the Z component of the world position.

##### Fixes :wrench:

- Fixed a bug where a glTF material with `alphaMode=BLEND` would be rendered as opaque if its `baseColorFactor` was not set.
- Fixed a crash that could occur when rapidly refreshing a tileset.
- Fixed crash when tilesets with point clouds were used in combination with Hardware Ray Tracing.
- Worked around an apparent Metal problem that prevented polygon clipping from working correctly on macOS.
- Fixed normals being incorrectly written to Runtime Virtual Texture output in tangent space instead of in world space.

In addition to the above, this release updates [cesium-native](https://github.com/CesiumGS/cesium-native) from v0.45.0 to v0.46.0. See the [changelog](https://github.com/CesiumGS/cesium-native/blob/main/CHANGES.md) for a complete list of changes in cesium-native.

### v2.14.1 - 2025-03-06

This file has been truncated. show original

Kevin_Ring · April 11, 2025, 8:59am

I believe v2.15.0 would have been available via the Epic Launcher by the time you posted your message. New versions sometimes don’t show up until you restart the Launcher, though.

In any case, thank you for the precise version. So this is the line you’re crashing on:

github.com/CesiumGS/cesium-unreal

Source/CesiumRuntime/Private/Cesium3DTileset.cpp

v2.14.1


      
            TRACE_CPUPROFILER_EVENT_SCOPE(Cesium::updateView)
            pResult = &this->_pTileset->updateView(frustums, DeltaTime);
          }
          updateLastViewUpdateResultState(*pResult);
          
          removeCollisionForTiles(pResult->tilesFadingOut);
          
          removeVisibleTilesFromList(
              _tilesToHideNextFrame,
              pResult->tilesToRenderThisFrame);
          hideTiles(_tilesToHideNextFrame);
          
          _tilesToHideNextFrame.clear();
          for (Cesium3DTilesSelection::Tile* pTile : pResult->tilesFadingOut) {
            Cesium3DTilesSelection::TileRenderContent* pRenderContent =
                pTile->getContent().getRenderContent();
            if (!this->UseLodTransitions ||
                (pRenderContent &&
                 pRenderContent->getLodTransitionFadePercentage() >= 1.0f)) {
              _tilesToHideNextFrame.push_back(pTile);
            }

Unfortunately, I don’t know what might cause that. Has this happened multiple times? Are you able to reproduce it consistently? Can you tell me how to reproduce it, preferably starting with the Cesium for Unreal Samples project?

Topic		Replies	Views
Build crash - EXCEPTION_ACCESS_VIOLATION from loading tiles Cesium for Unreal	8	1299	June 15, 2022
UE5.03 crashes log Cesium for Unreal	11	533	October 19, 2023
3D Tileset Crashing when Playing UE5 Cesium for Unreal	1	233	September 14, 2023
Built Project Crash at rapidjson Call v1.8.1 Cesium for Unreal	8	902	September 17, 2023
Render crash problem Cesium for Unreal	1	262	October 19, 2023

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION removeCollisionForTiles(pResult->tilesFadingOut);

Related topics