TypeError: Cannot set property 'geometry' of undefined

I’m rendering Cesium with Angular-Cesium. But this problem also occured when just running Cesium.js, which is Why I’m also posting here.

I’m rendering a kml stream and updating it every 1.5 seconds. Sometimes, it loads perfectly, no errors, and sometimes I get the error below. this is with no code changes. Also, If I set the interval to 10 seconds, It seems to solve the problem as far as I can tell… But of course, I’m trying to get an interval of 1.5 seconds.

My code is really simple, here is my Angular code. Notice the AfterViewInit hook.

export class GlobeComponent implements OnInit, AfterViewInit {
    cesiumViewer;
    options;
    kml$;

    constructor(private viewersManager: MapsManagerService,
                private globeService: GlobeService) {}

    ngOnInit() {
      // console.log(this.cesiumViewer);
    }

    ngAfterViewInit() {
        const viewer = this.viewersManager.getMap('main-map').getCesiumViewer()

        this.options = {
            camera: viewer.scene.camera,
            canvas: viewer.scene.canvas
        };

        this.kml$ = new Cesium.KmlDataSource(this.options);

        viewer.dataSources.add(
        this.kml$
        );

        setInterval(() => {
            this.kml$.load('http://..../rest/kml/accept/all', this.options);
        }, 1500);

    }
}

[NichijouCC]

createGeometryResults.length is > the instances.length ,so alert error.in my debug

[shunter]

I’m not sure which is the right fix. It seems dangerous for the batch to be directly manipulating the geometryInstances. I’m not sure from reading it whether the batch code was written with the awareness that the array is actually being shared or not. @mramato any recollections here?

Alternatively we could change packCombineGeometryParameters to just discard createGeometryResults for which we no longer have a geometryInstances. I guess they are correlated by index in the arrays. Maybe it needs to be smarter than that, since presumably adding new entities during CREATING could happen to, or we could delete then add and end up referencing the wrong geometry instance. This goes back to the danger of directly manipulating Primitive.geometryInstances externally from the batch, I guess.