Trying to diagnose a Cesium crash


What could be causing this error?

The trace is simply insufficient for me to pin-point the source of the bug.

Error Trace:

Fails in normalize() due to a cartesian3 equal to ZERO

CesiumWidget.js:691 An error occurred while rendering. Rendering has stopped.
DeveloperError: normalized result is not a number
at new DeveloperError (http://localhost:3000/cesium/Cesium.js:83:13)
at Function.Cartesian3.normalize (http://localhost:3000/cesium/Cesium.js:2103:13)
at pan3D (http://localhost:3000/cesium/Cesium.js:325542:18)
at spin3D (http://localhost:3000/cesium/Cesium.js:325342:9)
at reactToInput (http://localhost:3000/cesium/Cesium.js:323916:11)
at update3D (http://localhost:3000/cesium/Cesium.js:326135:5)
at ScreenSpaceCameraController.update (http://localhost:3000/cesium/Cesium.js:326323:7)
at Scene.initializeFrame (http://localhost:3000/cesium/Cesium.js:330265:39)
at CesiumWidget.render (http://localhost:3000/cesium/Cesium.js:348936:19)
at render (http://localhost:3000/cesium/Cesium.js:348190:20)

Stephan Marcotte, P.Eng.
m. (403) 975-5025

Can you provide more information? What items have you placed into the scene? Is the camera configured to follow an entity? Can you produce a Sandcastle example that exhibits the problem?


Hi Scott,

I cannot reproduce with a small enough Sandcastle sample, as the application is somewhat too large for that.

I have roughly 15 tile sets, each ranging from 1 to 500 features, as well as ~500 entities.

It happens when I try to move about the scene using CTRL-mouse drag. This is an intermittent bug.

Stephan Marcotte, P.Eng.
m. (403) 975-5025