Setting markerSize: 0 with large GeoJSON files causes Cesium to crash.

[arelenglish]

I've tested this on a MacBook Air with 8GB of memory and a MacBook Pro with 16GB of memory and experienced the issue. A Cesium forum user was unable to recreate the issue on her computer.

When adding a largish GeoJSON file (2,837 unique markers and polylines) to a map and setting the markerSize : 0 Cesium hangs and crashes WebGL after about 30 seconds of trying to render the map. Leaving markerSize its default size, or setting the color to transparent solves the issue, so my assumption is that setting markerSize uses a lot of memory. When the dataset is smaller, even up to 1,500 markers, Cesium doesn't crash or hang. Additionally, when I don't add the polylines Cesium has no issue when setting markerSize, but I don't know what would happen with extremely large datasets.

Here is a sandcastle where you can see the issue. I set markerSize : 0 on line 9. If you switch this to markerColor: Cesium.Color.fromHsl(0, 0, 0, 0) or just remove the line, the scene will render fine.

[hpinkos]

Hi @arelenglish
Your Sandcastle example loaded for me with no errors. Did you see an error message or anything when you tried to load it?

[NaderCHASER]

@hpinkos Issues are with Billboard->TextureAtlas->Texture.js calling copyFrom() here

Here is a screenshot of what I'm seeing in Chrome's Developer Tools.

[arelenglish]

I get a different error:

I'm not sure why it's working on some machines, and not on others.

The above error ultimately results in WebGL crashing.

[wrinkledcheese]

I have this issue in code I've written. I'm not doing any markers, but I am interested in any updates for this issue, as it may shed some light into my own issue.

[arelenglish]

@wrinkledcheese I think there is an issue with changing the size of the billboards. I got around this problem by just setting them to almost transparent. If you make them totally transparent, there is no clickable area.

My code looks something like this:

Cesium.GeoJsonDataSource.load(data, {
        stroke: Cesium.Color.fromBytes(0, 230, 240, 40),
        markerColor: Cesium.Color.fromHsl(0, 0, 0, 0.01)
      }).then(function(dataSource) {
        viewer.dataSources.add(dataSource);
        viewer.zoomTo(dataSource);
        var entities = dataSource.entities.values;

Using marker size with a large data set always caused a crash. As far as I know this issue hasn't been fixed.