can't free memory used by loading GeoJsonDataSource, even when not added to viewer

[Maarondesigns]

When calling GeoJsonDataSource.load multiple times the memory usage continues to rise and never goes back down, even when the datasource is never added to the viewer, no entities are created/shown and there is no way to 'unload' the datasource.

My use case is increasing polygon resolution as the user zooms in, and decreasing when not visible on the screen or zoomed out. Once the higher resolution is loaded the increased memory usage never goes down again.

Sandcastle example:
I can't really provide a sandcastle example because this requires loading external geojson files from somewhere.

Browser:
Chrome Version 84.0.4147.89
Operating System:
Windows 10.0.18362 Build 18362

[OmarShehata]

I can't really provide a sandcastle example because this requires loading external geojson files from somewhere.

@Maarondesigns the easiest way to reproduce this in Sandcastle is by uploading your GeoJSON to Cesium ion (https://cesium.com/ion) and loading it from there. That'll make it easier for us to investigate this issue.

[Maarondesigns]

Here is a sandcastle that hopefully captures what I am talking about. It loads the world in 110m resolution, then the USA and Russia at 10m on timeouts. The memory usage is less if you never add the datasources to the viewer, however it still increases each time and never goes back down. Just loading these 3 files the memory is hovering right around 100 Mb with nothing rendered at all. You can imagine this escalating quickly out of control when trying to render every country in the world in 10m resolution in this way.

[KeyboardSounds]

Hey @Maarondesigns I tweaked your example to use setInterval instead of setTimeout and I'm pretty sure I can reproduce this.

I won't upload the whole heap snapshot because it's 500MB but I left it running for a while and took a screenshot

Those 35x GeoJSON datasources at the top look mighty suspicious.

I might be missing something, but I think those data sources should be freed since they aren't being used anywhere else.

[Maarondesigns]

Yep @KeyboardSounds that’s what I experience. If you load those 35 Geojson sources during the lifetime of the app but delete the entities, the data source and any reference to them, they are still consuming almost the same memory as if you had all of them rendered in the scene at the same time.

[Maarondesigns]

Hello, is there an update or recommendation for this issue, or is it being looked into? This is potentially a show stopper for the company I work for to use Cesium. I am loading geojson data for states within a selected country and if you view more than 3 countries the memory is already above 300 MB and randomly jumps to 500 and back down thereafter, never going below 250, with 0 things rendered in the scene. This crashes the site on IOS making it unusable.

Is there anything I can do on my end? Removing all entities from the datasource and even removing the datasource from viewer does not effect memory usage.

[Maarondesigns]

[ggetz]

Reported in #10369

[edeles-navagis]

Hi, are there any updates about this issue?
Maybe someone can point out where I could probably start investigating in the codes?

[edeles-navagis]

We got this "out of memory" error when loading geojson layer.
Checking some primitives, we found out that polygons consumes a lot of time.
What we did to resolve it is just set the Arctype for entity.polygon.arcType to ArcType.GEODESIC.
Maybe the default is ArcType.RHUMB.

[GatorScott]

An alternative to hosting and drawing large collections of static geometry would be to host the data in a WMS/WMTS server like GeoServer which could serve the data as a transparent overlay to the basemap. Not sure if this would fit your needs or not.

[905807873]

Hello, I have also encountered this issue at present, but there is no solution. May I ask if anyone else knows how to solve it