1. When we try to render many images on the map, Cesium crashed with the following error (minified version also have similar failure)
DeveloperError: drawingBufferWidth must be greater than zero.
Error
at new DeveloperError (http://dev.localhost:38251/Scripts/CesiumUnminified/Cesium.js:540:19)
at PerspectiveOffCenterFrustum.getPixelDimensions (http://dev.localhost:38251/Scripts/CesiumUnminified/Cesium.js:50581:19)
at PerspectiveFrustum.getPixelDimensions (http://dev.localhost:38251/Scripts/CesiumUnminified/Cesium.js:50963:39)
at Camera.getPixelSize (http://dev.localhost:38251/Scripts/CesiumUnminified/Cesium.js:169386:38)
at updateBoundingVolume (http://dev.localhost:38251/Scripts/CesiumUnminified/Cesium.js:114230:44)
at BillboardCollection.update (http://dev.localhost:38251/Scripts/CesiumUnminified/Cesium.js:114429:9)
at EntityCluster.update (http://dev.localhost:38251/Scripts/CesiumUnminified/Cesium.js:119883:39)
at PrimitiveCollection.update (http://dev.localhost:38251/Scripts/CesiumUnminified/Cesium.js:201238:27)
at updatePrimitives (http://dev.localhost:38251/Scripts/CesiumUnminified/Cesium.js:210050:27)
at executeCommandsInViewport (http://dev.localhost:38251/Scripts/CesiumUnminified/Cesium.js:209911:13)
2. We have a GeoJson datasource that we load and then assign each of the entities a material of type ImageMaterial.
a typical image is https://landsat-pds.s3.amazonaws.com/L8/139/045/LC81390452014295LGN00/LC81390452014295LGN00_thumb_large.jpg
When we try to load many images (the number is about 2K in Chrome with NVIDIA Quadro K2000 on Chrome. The number depends on GPU and browser, IE crashing at couple of hundreds images and newer GPU allowing for more images).
3 Our system lets customers to search for Landsat images, select the ones they prefer and download them. We do not want to set artificial limits on the number of images user can select for preview on map, but want somehow trap the error without crashing Cesium, and ask the user to reduce the number of images rendered.
How can we do it?
4. We are using Cesium 1.40, but we've been seeing the error since we started to use the Cesium (it was probably 1.23) on windows 10, 8, 7
Thank you