I'm facing with some major performances issue when I try to load multiple KMZ at once in Cesium.
These performances issue exist in the 3 main browser but goes from lagish to browser crash depending on the browser.
This is caracterised mainly by a hich memory usage in the process where Cesium is hosted.
For example for Firefox it goes from 600 MB to 2.8 GB memory usage after trying to load multiple KMZ.
For test purpose, here is a simple code to try in sandcastle :
I use only one KMZ file of 40 KB with an underlying KML doc of 1000 KB for simplification.
If you try to reset with the reset option, you'll notice that memory does not go down significatly. Eventually after some back and forth between upload and reset, your browser will crash.
I first suspected a problem in the unzipped of kmz as this is where browser react very differently (seen in the network analysis from browser's developper tools), but the fact that memory does not go down after reset make me think that there might be another problem.
With garbage collector, maybe ?
The idea underlying this test was to load a huge KMZ file splitted into smaller ones
I'm using last Cesium version, from master git.
Thanks for your suggestions / ideas to resolve this problem.