Memory Usage Growth and SQLite Size Increase Issue in Unreal Engine 5.1 with Cesium3DTileset

[helion2017]

Subject: Memory Usage Growth and SQLite Size Increase Issue in Unreal Engine 5.1 with Cesium3DTileset

Issue Description: I have integrated Cesium3DTileset into Unreal Engine 5.1 with default parameters. While continuously rotating the camera using Tick, I observed a continuous increase in system memory usage, escalating from 6GB to 9GB within 10 minutes. Additionally, the size of cesium-request-cache.sqlite-wal grows from 1GB to 7GB during this time. In previous tests, the SQLite file reached 1TB within less than 24 hours, causing a memory crash. Since the camera is rotating in place, there should not be any new 3D tiles loaded. I am seeking insights into the possible causes of this issue and would appreciate any related usage recommendations.

Additional Information:

• Unreal Engine Version: 5.1
• Cesium3DTileset Parameters: Default
• Camera Behavior: Continuous rotation using Tick

Questions:

1. What might be causing the continuous increase in system memory usage?
2. Why does the size of cesium-request-cache.sqlite-wal keep growing during runtime?
3. Are there any specific usage recommendations or best practices to address this issue?

Note: I've observed similar issues in previous tests, where SQLite reached 1TB in less than 24 hours, resulting in a memory crash. Any guidance or insights into resolving this matter would be highly appreciated.

[csciguy8]

Thanks for the issue and detailed observations.

What Cesium3DTileset assets are you using? Cesium World Terrain? Google P3D Tiles? Point Clouds? etc.

Could relate to these issues too.. https://github.com/CesiumGS/cesium-native/issues/739 https://github.com/CesiumGS/cesium-native/issues/664

[helion2017]

Thanks for the issue and detailed observations.

What Cesium3DTileset assets are you using? Cesium World Terrain? Google P3D Tiles? Point Clouds? etc.

Could relate to these issues too.. CesiumGS/cesium-native#739 CesiumGS/cesium-native#664

Thank you for the prompt reply. Indeed, this issue seems closely related to the two mentioned above. I am working with a custom-handled oblique photogrammetry 3D Tileset, which was previously utilized in a CesiumJS project.