Added memory clean-up TODOs

src/World.js

@@ -5,6 +5,8 @@ import Point from './geo/Point';
 import LatLon from './geo/LatLon';
 import Engine from './engine/Engine';
 
+// TODO: Make sure nothing is left behind in the heap after calling destroy()
+
 // Pretty much any event someone using ViziCities would need will be emitted or
 // proxied by World (eg. render events, etc)
 

src/layer/Layer.js

@@ -2,6 +2,8 @@ import EventEmitter from 'eventemitter3';
 import THREE from 'three';
 import Scene from '../engine/Scene';
 
+// TODO: Make sure nothing is left behind in the heap after calling destroy()
+
 class Layer extends EventEmitter {
   constructor() {
     super();

src/layer/environment/EnvironmentLayer.js

@@ -3,6 +3,8 @@ import extend from 'lodash.assign';
 import THREE from 'three';
 import Skybox from './Skybox';
 
+// TODO: Make sure nothing is left behind in the heap after calling destroy()
+
 class EnvironmentLayer extends Layer {
   constructor(options) {
     super();

src/layer/environment/Skybox.js

@@ -2,6 +2,8 @@ import THREE from 'three';
 import Sky from './Sky';
 import throttle from 'lodash.throttle';
 
+// TODO: Make sure nothing is left behind in the heap after calling destroy()
+
 var cubemap = {
   vertexShader: [
 		'varying vec3 vPosition;',

src/layer/tile/GeoJSONTile.js

@@ -9,6 +9,8 @@ import extend from 'lodash.assign';
 import GeoJSON from '../../util/GeoJSON';
 import Buffer from '../../util/Buffer';
 
+// TODO: Make sure nothing is left behind in the heap after calling destroy()
+
 // TODO: Perform tile request and processing in a Web Worker
 //
 // Use Operative (https://github.com/padolsey/operative)

src/layer/tile/GeoJSONTileLayer.js

@@ -4,6 +4,8 @@ import GeoJSONTile from './GeoJSONTile';
 import throttle from 'lodash.throttle';
 import THREE from 'three';
 
+// TODO: Make sure nothing is left behind in the heap after calling destroy()
+
 // TODO: Consider pausing per-frame output during movement so there's little to
 // no jank caused by previous tiles still processing
 

src/layer/tile/ImageTile.js

@@ -2,6 +2,8 @@ import Tile from './Tile';
 import BoxHelper from '../../vendor/BoxHelper';
 import THREE from 'three';
 
+// TODO: Make sure nothing is left behind in the heap after calling destroy()
+
 class ImageTile extends Tile {
   constructor(quadcode, path, layer) {
     super(quadcode, path, layer);

src/layer/tile/ImageTileLayer.js

@@ -5,6 +5,8 @@ import throttle from 'lodash.throttle';
 import THREE from 'three';
 import extend from 'lodash.assign';
 
+// TODO: Make sure nothing is left behind in the heap after calling destroy()
+
 // DONE: Find a way to avoid the flashing caused by the gap between old tiles
 // being removed and the new tiles being ready for display
 //

src/layer/tile/Tile.js

@@ -2,6 +2,8 @@ import Point from '../../geo/Point';
 import LatLon from '../../geo/LatLon';
 import THREE from 'three';
 
+// TODO: Make sure nothing is left behind in the heap after calling destroy()
+
 // Manages a single tile and its layers
 
 var r2d = 180 / Math.PI;

src/layer/tile/TileCache.js

@@ -1,5 +1,7 @@
 import LRUCache from 'lru-cache';
 
+// TODO: Make sure nothing is left behind in the heap after calling destroy()
+
 // This process is based on a similar approach taken by OpenWebGlobe
 // See: https://github.com/OpenWebGlobe/WebViewer/blob/master/source/core/globecache.js
 

src/layer/tile/TileLayer.js

@@ -3,6 +3,8 @@ import extend from 'lodash.assign';
 import TileCache from './TileCache';
 import THREE from 'three';
 
+// TODO: Make sure nothing is left behind in the heap after calling destroy()
+
 // TODO: Consider keeping a single TileLayer / LOD instance running by default
 // that keeps a standard LOD grid for other layers to utilise, rather than
 // having to create their own, unique LOD grid and duplicate calculations when