Google tiles and switch level crash in Build

Wukovsky1 · April 9, 2025, 8:52am

Hi! I have a problem with crash in build for Win with Google tiles.
UE 5.3.2 cesium 2.15 from marketplace
I have google realistic tiles, static mesh buildings and a rasteroverlaypolygon to cut tiles for each of 3 different levels (sites). Also i have buttons to switch between levels (simple open level by ref). Everything is fine in editor, builds fine with no errors but built app always crashes when opening level (deleting tileset i guess). Deleting polygon components manually in editor solves the crash, but deleting polygon component in blueprint before opening another level doesnt help. I made new project with just 3 levels of google tiles and polygon clipping and simple switch between levels with keyboard, it also crashes in built app.
UPD. btw switching from google tiles to bing seems to solve the problem but id like to use google tiles

Summary

[2025.04.08-08.35.11:151][427]LogWindows: Error: === Critical error: ===
[2025.04.08-08.35.11:151][427]LogWindows: Error:
[2025.04.08-08.35.11:151][427]LogWindows: Error: Fatal error!
[2025.04.08-08.35.11:151][427]LogWindows: Error:
[2025.04.08-08.35.11:151][427]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffffffffffff
[2025.04.08-08.35.11:151][427]LogWindows: Error:
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79b139a3d texas_project.exe!CesiumRasterOverlays::RasterOverlayTile::~RasterOverlayTile()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae2a748 texas_project.exe!std::vector<Cesium3DTilesSelection::RasterMappedTo3DTile,std::allocatorCesium3DTilesSelection::RasterMappedTo3DTile >::_Tidy()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae296f9 texas_project.exe!std::_Destroy_range<std::allocatorCesium3DTilesSelection::Tile >()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae2a7ed texas_project.exe!std::vector<Cesium3DTilesSelection::Tile,std::allocatorCesium3DTilesSelection::Tile >::_Tidy()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae29719 texas_project.exe!std::_Destroy_range<std::allocatorCesium3DTilesSelection::Tile >()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae2a7ed texas_project.exe!std::vector<Cesium3DTilesSelection::Tile,std::allocatorCesium3DTilesSelection::Tile >::_Tidy()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae29719 texas_project.exe!std::_Destroy_range<std::allocatorCesium3DTilesSelection::Tile >()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae2a7ed texas_project.exe!std::vector<Cesium3DTilesSelection::Tile,std::allocatorCesium3DTilesSelection::Tile >::_Tidy()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae29719 texas_project.exe!std::_Destroy_range<std::allocatorCesium3DTilesSelection::Tile >()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae2a7ed texas_project.exe!std::vector<Cesium3DTilesSelection::Tile,std::allocatorCesium3DTilesSelection::Tile >::_Tidy()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae29719 texas_project.exe!std::_Destroy_range<std::allocatorCesium3DTilesSelection::Tile >()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae2a7ed texas_project.exe!std::vector<Cesium3DTilesSelection::Tile,std::allocatorCesium3DTilesSelection::Tile >::_Tidy()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae29719 texas_project.exe!std::_Destroy_range<std::allocatorCesium3DTilesSelection::Tile >()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae2a7ed texas_project.exe!std::vector<Cesium3DTilesSelection::Tile,std::allocatorCesium3DTilesSelection::Tile >::_Tidy()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae29719 texas_project.exe!std::_Destroy_range<std::allocatorCesium3DTilesSelection::Tile >()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae2a7ed texas_project.exe!std::vector<Cesium3DTilesSelection::Tile,std::allocatorCesium3DTilesSelection::Tile >::_Tidy()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae29719 texas_project.exe!std::_Destroy_range<std::allocatorCesium3DTilesSelection::Tile >()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae2a7ed texas_project.exe!std::vector<Cesium3DTilesSelection::Tile,std::allocatorCesium3DTilesSelection::Tile >::_Tidy()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae29719 texas_project.exe!std::_Destroy_range<std::allocatorCesium3DTilesSelection::Tile >()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae2a7ed texas_project.exe!std::vector<Cesium3DTilesSelection::Tile,std::allocatorCesium3DTilesSelection::Tile >::_Tidy()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae43131 texas_project.exe!Cesium3DTilesSelection::Tile::`scalar deleting destructor’()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae408c4 texas_project.exe!Cesium3DTilesSelection::TilesetContentManager::~TilesetContentManager()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae3fd23 texas_project.exe!Cesium3DTilesSelection::TilesetContentManager::TilesetContentManager()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae3d84d texas_project.exe!async::task::then<async::detail::inline_scheduler_impl,async::detail::unwrapped_func<async::detail::fake_void,async::task > >()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae37f3c texas_project.exe!Cesium3DTilesSelection::RasterizedPolygonsTileExcluder::shouldExclude()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff7970791ca texas_project.exe!async::detail::task_base::run_continuationasync::detail::inline_scheduler_impl() [D:\build\U5M\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\CesiumForUnreal\Source\ThirdParty\include\async++\task_base.h:101]
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae37fdc texas_project.exe!Cesium3DTilesSelection::RasterizedPolygonsTileExcluder::shouldExclude()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79709c7d6 texas_project.exe!async::detail::task_base::run_continuations() [D:\build\U5M\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\CesiumForUnreal\Source\ThirdParty\include\async++\task_base.h:113]
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae37dc8 texas_project.exe!Cesium3DTilesSelection::RasterizedPolygonsTileExcluder::shouldExclude()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae82efb texas_project.exe!CesiumAsync::CesiumImpl::QueuedScheduler::dispatchInternal()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79ae82f6a texas_project.exe!CesiumAsync::CesiumImpl::QueuedScheduler::dispatchQueuedContinuations()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff797088a8f texas_project.exe!ACesium3DTileset::IsReadyForFinishDestroy() [D:\build\U5M\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\CesiumForUnreal\Source\CesiumRuntime\Private\Cesium3DTileset.cpp:2276]
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff7905ddbe2 texas_project.exe!FProperty::ImportText_Internal()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff7905de6e5 texas_project.exe!IncrementalPurgeGarbage()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79058692c texas_project.exe!UE::GC::CollectGarbageImpl<1>()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff7905afe11 texas_project.exe!CollectGarbage()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff7905afc75 texas_project.exe!CollectGarbage()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79684ac0a texas_project.exe!UEngine::TrimMemory()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff7968170f0 texas_project.exe!UEngine::LoadMap()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff7967adc68 texas_project.exe!UEngine::Browse()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff796843b29 texas_project.exe!UEngine::TickWorldTravel()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff795a25afb texas_project.exe!UGameEngine::Tick()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff796ff5323 texas_project.exe!FEngineLoop::Tick()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79700d05c texas_project.exe!GuardedMain()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79700d13a texas_project.exe!GuardedMainWrapper()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79700ffe6 texas_project.exe!LaunchWindowsStartup()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79701fbd4 texas_project.exe!WinMain()
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ff79b6965fa texas_project.exe!__scrt_common_main_seh() [D:\a_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288]
[2025.04.08-08.35.11:151][427]LogWindows: Error: [Callstack] 0x00007ffcaa76e8d7 KERNEL32.DLL!UnknownFunction
[2025.04.08-08.35.11:151][427]LogWindows: Error:
[2025.04.08-08.35.11:156][427]LogExit: Executing StaticShutdownAfterError
[2025.04.08-08.35.11:157][427]LogWindows: FPlatformMisc::RequestExit(1, LaunchWindowsStartup.ExceptionHandler)
[2025.04.08-08.35.11:157][427]LogWindows: FPlatformMisc::RequestExitWithStatus(1, 3, LaunchWindowsStartup.ExceptionHandler)
[2025.04.08-08.35.11:157][427]LogCore: Engine exit requested (reason: Win RequestExit)

Wukovsky1 · April 10, 2025, 5:17am

My guess is the crash is caused by destroying tileset when it’s still async loading tiles. I think I’ve seen a topic about it, but can’t find it now. Then I tried to suspend update before destroying it, it didn’t work out. Unfortunately I don’t know C++, is there a way to do it in BP, event on ending loading or smth? But I have no idea what it has to do with deleting RasterOverlayPolygon, deleting the component seem to fix the problem but if the component exists even with no polygons assigned - it crashes

janine · April 11, 2025, 2:10pm

Hi @Wukovsky1, welcome to the community!

Thank you for including all the details in your post. Do you have steps for building a minimal level that reproduces this behavior? We’d like to replicate it on our end so we can better troubleshoot this issue, and having instructions will help. Thank you!

Wukovsky1 · April 11, 2025, 3:09pm

Hi!
1.create new blank project (NewWorld)
2.(turn on cesium plugin, connect to cesium ion) add Google Photorealistic Tiles
3.create any CesiumCartographicPolygon
4.add CesiumPolygonRasterOverlay component to the tileset, add the polygon
5.duplicate the level (NewWorld1)
6.add logic for level switch: for example in NewWorld level blueprint I use button “1” to open level (by ref) NewWorld1, in NewWorld1 level blueprint button “2” to open level (by ref) NewWorld.
7. package the project and it will crash when switching levels. not always! sometimes first switch, sometimes 7-8 time you switch.

In my real project it happens 100% when switching between two levels, but anyway crash logs are the same as in 1 message here

Timothy_Eccleston · April 14, 2025, 3:41pm

Having the exact same issue on build with my project. It specifically happens on unload, as I start in a cesium level and move to a level without cesium. Same error messages and crash.

Wukovsky1 · April 22, 2025, 10:34am

Hi! Any updates? Have you managed to reproduce the issue on your side or maybe we should send a project/packaged?

Kevin_Ring · April 22, 2025, 12:04pm

Hi @Wukovsky1,
Thanks for providing the steps. I can reproduce this in a Debug build as an assertion failure. I wrote an issue for it here:

github.com/CesiumGS/cesium-unreal

Assertion failure / undefined behavior when leaving a level with a CesiumCartographicPolygon

opened 12:02PM - 22 Apr 25 UTC

kring

bug urgent

Originally reported here: https://community.cesium.com/t/google-tiles-and-switch…-level-crash-in-build/39891 Here's a slight variation on the user's reproduction steps that will be a little easier to do in a development environment, and results in an assertion failure. Presumably the user's crash in shipping builds is undefined behavior that happens later as a result of the violation of the invariant. 1. Create a new Empty Level. 2. Add Cesium SunSky, Google Photorealistic 3D Tiles, and a Cesium Cartographic Polygon using the Cesium panel. 3. Add a Cesium Polygon Raster Overlay component to the Google Actor. Add a new item to the Polygons property and point it at the CesiumCartographicPolygon. 4. Save the new level. 5. Use File -> Save Current Level As to duplicate the level to another name. 6. Open the Level Blueprint and add some nodes so that a keypress opens the _other_ level that you just created. 7. Open that other level, and its Level Blueprint, and add some nodes to make a keypress open the other other level. The idea is that a key can be used to switch between the two levels during play. ![Image](https://github.com/user-attachments/assets/83a5bcc4-6376-4517-9660-f36ddb799824) 8. Start Play-in-Editor on either level. Press the key to switch to the other one. Keep pressing it until you hit an assertion failure. The failed assertion is in the `RasterOverlayTileProvider` destructor: ```cpp // Explicitly release the placeholder first, because RasterOverlayTiles must // be destroyed before the tile provider that created them. if (this->_pPlaceholder) { CESIUM_ASSERT(this->_pPlaceholder->getReferenceCount() == 1); this->_pPlaceholder = nullptr; } ``` The call stack looks like this: ``` UnrealEditor-CesiumRuntime-Win64-DebugGame.dll!CesiumRasterOverlays::RasterOverlayTileProvider::~RasterOverlayTileProvider() Line 89 C++ [External Code] UnrealEditor-CesiumRuntime-Win64-DebugGame.dll!CesiumUtility::ReferenceCounted<CesiumRasterOverlays::RasterOverlayTileProvider,0>::releaseReference() Line 89 C++ UnrealEditor-CesiumRuntime-Win64-DebugGame.dll!CesiumUtility::IntrusivePointer<CesiumRasterOverlays::RasterOverlayTileProvider>::releaseReference() Line 230 C++ UnrealEditor-CesiumRuntime-Win64-DebugGame.dll!CesiumUtility::IntrusivePointer<CesiumRasterOverlays::RasterOverlayTileProvider>::~IntrusivePointer<CesiumRasterOverlays::RasterOverlayTileProvider>() Line 69 C++ [External Code] UnrealEditor-CesiumRuntime-Win64-DebugGame.dll!Cesium3DTilesSelection::RasterOverlayCollection::remove(const CesiumUtility::IntrusivePointer<CesiumRasterOverlays::RasterOverlay> & pOverlay) Line 225 C++ UnrealEditor-CesiumRuntime-Win64-DebugGame.dll!UCesiumRasterOverlay::RemoveFromTileset() Line 128 C++ UnrealEditor-CesiumRuntime-Win64-DebugGame.dll!ACesium3DTileset::DestroyTileset() Line 1236 C++ UnrealEditor-CesiumRuntime-Win64-DebugGame.dll!ACesium3DTileset::EndPlay(const EEndPlayReason::Type EndPlayReason) Line 2087 C++ UnrealEditor-Engine.dll!AActor::RouteEndPlay(const EEndPlayReason::Type EndPlayReason) Line 2716 C++ UnrealEditor-Engine.dll!UEngine::LoadMap(FWorldContext & WorldContext, FURL URL, UPendingNetGame * Pending, FString & Error) Line 14853 C++ ```

I don’t know exactly what causes it just yet, but keep an eye on that issue for updates.

Thanks for reporting it!

Wukovsky1 · April 27, 2025, 4:22pm

Thank you so much for investigating the issue, hope to see fix in May update!

Topic		Replies	Views
Crash with Google tiles Cesium for Unreal	14	538	February 14, 2025
Packaged Application Crashing Cesium for Unreal	5	214	January 4, 2024
Crashing when a Cesium title loads and we switch levels Cesium for Unreal	6	500	October 26, 2022
Bug when generating Cesium Tiles in runtime Cesium for Unreal	4	76	August 23, 2024
Crash with Google Photorealistic 3D Tiles - fix now available for UE 5.1 - 5.5 Cesium for Unreal	9	185	February 24, 2025

Google tiles and switch level crash in Build

Related topics