Memory leak : (1) added terrain; (2) set position [-100,90,0] or [-100,90,100]

I added the terrain and set this geographic coordinate in north polle, and there was a memory leak.
And I can’t control the earth;

 const viewer = new Cesium.Viewer('cesiumContainer', {
        terrain: new Cesium.Terrain(
            new Cesium.EllipsoidTerrainProvider()
viewer.terrainProvider = await Cesium.createWorldTerrainAsync({});
document.getElementById("test111").addEventListener('click', () => {{
            destination: Cesium.Cartesian3.fromDegrees(
                // 100
            orientation: {
                heading: 0,
                pitch: -1.5707963267948966,
                roll: 0

About 5 seconds later, the page crashes;

I have no control over what coordinates and heights the user uses ,

So what should I do to fix the crash?


Unfortunately, I don’t have an idea (yet) about how to resolve this.

But I also observed this crash, and from a mix of observing the network tab and semi-educated guesses, it looks like it is trying to load … too many tiles because of the liling scheme: There are “infinitely many” tiles coming together at the north pole (because it is surrounded by a “triangle fan” of tiles), and depending on how close the camera is, it will try to load all of them (or at least, far too many of them).

@Gabby_Getz Unless you disagree, I’d open an issue with some details about that.

I’ve seen similar behavior reported with polygons crossing the poles, but not around moving the camera there.

The tiling scheme is definitely a plausible cause.

Let’s open an issue.

That linked issue seems to talk about a ‘normalized-result-is-not-a-number’ crash, and not about an out of memory error. There is some strong evidence that the crash here is caused by the “infinite” number of tiles at the north pole. I’ve opened Out of memory when looking at north pole · Issue #11879 · CesiumGS/cesium · GitHub with a first (very basic) step of analyzing this.

Thanks for your help.