Cesium memory usage in Chrome

Some of you may have noticed that Cesium memory usage in Chrome seems to continually grow. We recently ran into an issue where it grew until Chrome crashed. For example, you would see this if you update a large polyline’s positions every frame. We submitted a Chrome bug:


It will help them prioritize the issue if you could “star” it (visit the above link and click on the star image) so they know people are interested.

Thank you,


Hi Daniel,

Above issue exists in IE also. Do we need to submit a bug with IE also or is there any workaround for this?