Cesium 1.28 Bug ?

Steps to reproduce:

  1. open a new anonymous / private windows in chrome / firefox
  2. Move and Zoom very fast (right mouse button and drag, rather than scroll wheel) to tile with coordinates 0,0
    I’m attaching screenshots with the error, it throws different errors in firefox and chrome, not tested with other browsers.

I’m not sure if it’s a bug with Cesium but it seems like this. Didn’t happen in 1.26.

Other than that let me tell I’m fascinated with the speed improvements in the new version. I discovered this bug playing around and enjoying how fast everything loads.


I wasn’t able to reproduce this in master, so it’s possible it will be fixed in the 1.29 release.

What OS are you using?

Could you post the crash message from the unminified version of Cesium? That way I can see which functions are failing.



I’m running Ubuntu, 16.04, and the server on which I test Cesium also runs Ubuntu 16.04. I tested again with Cesium 1.28 Unminified, on Firefox, and I am attaching a screenshot with the error. I wasn’t able to reproduce it on Chrome with Cesium Unminified though.

Thanks for the information! I filed a bug report here: https://github.com/AnalyticalGraphicsInc/cesium/issues/4755
I wasn’t able to reproduce it, but we’ll see if someone else on the team is able to so we can figure out what’s going on.



Hi Hannah,
It seems that I had some tiles missing around tile 0,0 , at the uppermost layer and I’m now quite convinced this was the reason for the error. It’s interesting that it only happened sometimes and I thought it’s a bug. I’m rechecking all my tiles now. So sorry for the false alarm.


I think the crash you’re seeing was fixed in this pull request: https://github.com/AnalyticalGraphicsInc/cesium/pull/4763

It will be included in the 1.29 release available January 2nd.

If you still see the crash after that, let me know. Thanks!


So, yesterday (19 Dec 2016) I downloaded the latest changes from master branch, and built Cesium, but I’m still getting the same error even with this build, unfortunately. Meanwhile I had all my missing tiles fixed if that matters. I’ve noticed the error happens around meridian 0, at any of the poles - north or south. You first have to move to position around meridian 0, and then zoom (it may be not that fast as I initially suggested) to any of the poles. I’m attaching my index.html file if any of the developers would like to test. It’s setup with the urls of my server, and I have enabled CORS, so just upload the file on your web server and run it.

index.html (4.25 KB)

Update: I’m able to reproduce it in sandcastle, here’s code to test:

var viewer = new Cesium.Viewer(‘cesiumContainer’, {
baseLayerPicker : true

var layers = viewer.imageryLayers;
var coordinateTiles = layers.addImageryProvider(Cesium.createOpenStreetMapImageryProvider({
url : ‘http://commercialplanet.eu/cesium/data6/coordinatestiles’,
maximumLevel : 11,
credit : ‘’

  • the same bug happens with different tile layer loaded (so probably not related to broken tiles).
    -it happens when zoomed between tiles with X coordinates 2047, 0 and any of the poles, as well as the opposite side of the globe - between tiles 1023, 1024 and any of the poles (places where one side is loaded and other is still blurry and loading)
    -the bug only happens on the first load. If it doesn’t happen on the first try, the example needs to be restarted and then try again.

Thanks for providing the example! I was able to reproduce it with that. I’ve submitted a new issue here: https://github.com/AnalyticalGraphicsInc/cesium/issues/4777



For those following this thread, Kevin fixed this in #4811, which will be in Cesium 1.30 in February.