Matthew Amato

Given we've had various issues with clustering, this sounds like something that should be fixed sooner rather than later. Do we understand how this bug manifests in actual clustering behavior?

> It also doesn't crash when scene3DOnly = true That's because we don't need to split the geometry in 3D so this code path never gets calls.

We definitely need to delete them because having an object with that many properties (even undefined) has an adverse affect on performance and memory, but I agree that doing it...

> slowly approaching writing your own hashtable data structure, so perhaps we should just do that directly. This is the heart of one of the main memory/performance bottlenecks in Cesium....

@OmarShehata I see the 1.59 behavior in 1.61 too: 

I think this may be multiple issues, but that test case had a lot of noise/useless settings. HEre is a reduced test case that shows the problem. ```js var viewer...

@lilleyse thoughts?

It might be time to start considering auto-normalizing vectors in certain places. The main reason we don't do it is for performance reasons, but I feel like it bites us...

This is a good start. Let's concentrate on Placemark and geometry first. We can just render point geometry as default billbboards and everything else as white lines and polygons. This...

Hey @andre-nunes. I haven't worked directly on KML in a little while but #1444 adds some major features that we needed in order to move forward (such as extruded polygons),...