Huge memory leaks with rendering images as entities

Is there anything wrong with the below code. What I am doing is

  1. Remove all imagery layers from the globe
  2. Add world map as a border using geoJson
  3. Add 10 radar images of resolution 4096 * 3500 each as entities to the viewer.
  4. Then by slider(range 1 - 10), I show only that radar image that the current slider value is.

It works fine but there is huge memory leak. Like my MAC machine keeps getting slow. On iPhone, it even crashes the application and restarts it after ~2 minute

var cesiumContent = {};
var radarEntitiesList = [];
cesiumContent.showHideRadarForSlider = function() {
    radarEntitiesList.forEach(function(item, index) { = false;
        if (index === currentSliderIndex) {
   = true;
cesiumContent.addRadarToCesium = function() {
    for (var i = 0; i < 10; i++) {
        var temp = viewer.entities.add({
            name: `${i + 1} Rotating rectangle with rotating texture coordinate `,
            rectangle: {
                coordinates: Cesium.Rectangle.fromDegrees(-130.0000000, 20, -60.0000020, 55.0000000),
                material: `static/img/radar/${i + 1}.png`,
                classificationType: Cesium.ClassificationType.TERRAIN,
cesiumContent.addWorldBorder = function(world) {
    var globeWaterColor = Cesium.Color.fromCssColorString("#010d12");
    var landColor = Cesium.Color.fromCssColorString("#243e54");
    var scene = viewer.scene;
    var globe = scene.globe; = false;
    scene.fog.enabled = false;
    scene.globe.showGroundAtmosphere = false;
    globe.baseColor = globeWaterColor;
        Cesium.GeoJsonDataSource.load("static/json/world-110m.json", {
            stroke: Cesium.Color.WHITE,
            fill: landColor,
            strokeWidth: 1,
content.createCesium = function(world) {
    Cesium.Ion.defaultAccessToken = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJqdGkiOiI3NDY2YTkwNC01ZTQxLTQ2MzktYmQyZi02YTY0YjRhMTMzNGUiLCJpZCI6MTczOTQsInNjb3BlcyI6WyJhc3IiLCJnYyJdLCJpYXQiOjE1NzIxNzMyMzl9.93BT_28Av3mBeD6J--cH1eebHfeHMSyNfjh4E28r6gE';
// Intitalize cesium
    viewer = new Cesium.Viewer('cesiumContainer', {
        fullscreenButton: false,
        timeline: false,
        animation: false,
        baseLayerPicker: false,
        sceneModePicker: false,
// remove all layers so it is blank globe
 // draw world map border as vectors
// add 10 png images to cesium viewer.

Since you’re not actually adding/removing any entities, I wouldn’t expect there to be a memory leak. Have you verified by looking at the Chrome developer tools that memory is indeed increasing? Can you tell exactly what is causing it?

If you can share a reproducible example in Sandcastle that would help. See: How to share custom Sandcastle examples

Could the leak be on the WebGL “side” of things? 10 x 4096 x 3500 is a pretty beefy texture load on its own, but if something about this arrangement is causing the textures to be duplicated due to e.g. a texture atlas bug, I could see (available-to-browser) video memory filling up. Is the Chrome performance tab going to give you that information?