An error occurred while rendering -> unpackCombineGeometryParameters?

Sometimes loading my cesium project the rendering stops on init and the console shows this message
this happens a lot in firefox 55.0.2 (64-bit),
and sometimes in chrome 59.0.3071.104 (Build oficial) (64 bits)…

An error occurred while rendering. Rendering has stopped.
TypeError: d is undefined

My projects loads 4 geojsons of 400kb each one, not so much…

The cesium version is 1.35

Hi Pablo,

Could you provide a sample of the data and maybe also a code snippet in Sandcastle? It looks like you’re using the built & minified version of Cesium so there’s not a lot of information in that error message.



I have the same problem, sometimes an error pops up. (See attached image
I can't trace the problem but it might be one of the following (at least I suspect it, placed a break-point at these lines and traced back where it came from).
Either a use of Cylinder or Polyline worker stopped at the mentioned break-point. I don't know if it has something to do with it, but at least in my case after creating a cylinder, based one radius, i use EllipseGeometryLibrary.computeEllipsePositions and afterwords I use Cartesian3.unpackArray. From that array creating a Polyline.
(Similar to the following code);

var ellipse2 = Cesium.EllipseGeometryLibrary.computeEllipsePositions({
    semiMinorAxis: 300000,
    semiMajorAxis: 300000,
    rotation: 0,
    center: Cesium.Cartesian3.fromDegrees(-100, 34),
    granularity: Cesium.Math.RADIANS_PER_DEGREE
}, false, true);
var innerPositions = Cesium.Cartesian3.unpackArray(ellipse2.outerPositions);

Again I am not sure if that is related but I need to find a solution ASAP, and that is the only lead I have.

Hi Matan,

EllipseGeometryLibrary is not part of the public API, so we don’t recommend using it directly. Can you try using EllipseGeomtery to accomplish your task?



Hey Gabby,

I use that API to create a ring (more like a doughnut). I have found this code from another answer.
(!topic/cesium-dev/LYYiAyXOsis See Hannah's answer) It did actually work.
Again this is not the main question, I just thought it might generate the bug. The problem I am facing is hard to trace.

The error seems to be happening in a web worker. This means something is not happening correctly at render time. You can try running with the Cesium Source code instead of the built version as you may get better error messages. The problem is, if you’re not using the public API, we can’t guarantee something hasn’t changed under the hood, and your code may no longer work.