Strange bug with custom primitive

I’m creating a custom primitive, basically a cone/pyramid/frustum that will project a texture into the terrain.
It renders fine, but when I put a certain rotation matrix on the primitive, it suddenly gives a weird exception.
As you can see, it is somehow related to splitting the geometry down longitude lines.
Why this is done automatically be Cesium?
It is necessary? Anyway to disable or avoid the exception by somehow modifying the geometry?

DeveloperError: All attribute lists must have the same number of attributes.

Error
at new DeveloperError (http://localhost:8080/Build/Cesium/Cesium.js:1282:19)
at Function.Geometry.computeNumberOfVertices (http://localhost:8080/Build/Cesium/Cesium.js:16366:27)
at updateGeometryAfterSplit (http://localhost:8080/Build/Cesium/Cesium.js:26880:41)
at updateInstanceAfterSplit (http://localhost:8080/Build/Cesium/Cesium.js:26919:24)
at splitLongitudeLines (http://localhost:8080/Build/Cesium/Cesium.js:27234:9)
at Object.GeometryPipeline.splitLongitude (http://localhost:8080/Build/Cesium/Cesium.js:27484:17)
at geometryPipeline (http://localhost:8080/Build/Cesium/Cesium.js:76666:34)
at Object.PrimitivePipeline.combineGeometry (http://localhost:8080/Build/Cesium/Cesium.js:76889:26)
at Primitive.update (http://localhost:8080/Build/Cesium/Cesium.js:78303:48)
at VisionConePrimitive.update (http://localhost:8080/Apps/Inovaworks/VisionConePrimitive.js:659:26)
at PrimitiveCollection.update (http://localhost:8080/Build/Cesium/Cesium.js:119944:27)
at updatePrimitives (http://localhost:8080/Build/Cesium/Cesium.js:125271:27)
at render (http://localhost:8080/Build/Cesium/Cesium.js:125324:9)
at Scene.render (http://localhost:8080/Build/Cesium/Cesium.js:125365:13)
at CesiumWidget.render (http://localhost:8080/Build/Cesium/Cesium.js:134707:25)
at render (http://localhost:8080/Build/Cesium/Cesium.js:134182:32)

The splitting is required for 2D and Columbus View visualization. If you onyl care about 3D, you can specify scene3DOnly : true in the Viewer constructor.

That being said, this error usually indicates a bug in the custom primitive. If you’re still having this issue, can you post your code for us to look at?