Crash when removing multiple CustomDataSources with CallbackProperties

Forum link

Sandcastle

Clicking “remove” will throw the following error (I’m showing the unminified error):

DeveloperError: This object was destroyed, i.e., destroy() was called.
Error
    at new DeveloperError (http://localhost:8080/Source/Core/DeveloperError.js:43:19)
    at PolylineCollection.throwOnDestroyed (http://localhost:8080/Source/Core/destroyObject.js:45:19)
    at PrimitiveCollection.update (http://localhost:8080/Source/Scene/PrimitiveCollection.js:369:27)
    at PrimitiveCollection.update (http://localhost:8080/Source/Scene/PrimitiveCollection.js:369:27)
    at PrimitiveCollection.update (http://localhost:8080/Source/Scene/PrimitiveCollection.js:369:27)
    at updateAndRenderPrimitives (http://localhost:8080/Source/Scene/Scene.js:2937:27)
    at executeCommandsInViewport (http://localhost:8080/Source/Scene/Scene.js:2776:13)
    at updateAndExecuteCommands (http://localhost:8080/Source/Scene/Scene.js:2584:13)
    at render (http://localhost:8080/Source/Scene/Scene.js:3224:9)
    at tryAndCatchError (http://localhost:8080/Source/Scene/Scene.js:3244:13)

This only happens under very specific conditions. It will NOT happen if:

• You comment out one of the datasources.add lines like viewer.dataSources.add(dataSource2);
• If only one of the entities has a callback property (try uncommenting the positions line positions : Cesium.Cartesian3.fromDegreesArray(poss1))

It also works fine if you remove the entities directly from each dataSource, as opposed to removing the dataSource itself.

There aren’t any Sandcastle examples using CustomDataSource to group entities this way, so I’m not sure if this is expected. My workaround is to just store the entities yourself in an array and handle iterating through and removing when you need to remove a group.

[mangodudemartin]

hello, team. I’m having this same issue and wanted to check on the status of the bug fix. Are there any other identified workarounds at this time?

I’m using Resium in a React project, and whenever I have more than one CustomDataSource that includes a PolylineGraphics Entity that is using a CallbackProperty I will receive this same error when navigating to another page within the application. Removing the CallbackProperty, the PolylineGraphics Entity, or the additional CustomDataSources resolves the issue.

[yfrans]

Same here. Using resium, drawing Polyline with CallbackProperty as the positions argument of the Polyline. The app crashes when calling viewer.datasources.remove(data_source) when data_source contains the Polyline with the CallbackProperty. Using Polyline without CallbackProperty resolve the issue, but we need the CallbackProperty since we update the position of the Polyline multiple times/sec.

Edit: added sandcastle example https://sandcastle.cesium.com/#c=tVRdb9owFP0rV+wFJOrYTpzYQNEkJu1l0qox7WXZg5u4xWo+UOzQsan/fTekFGhZ1T3sAck3+Byfc318gwA+aK+XddtkBhpT1hsDWaPdCsxPXa4LM4GV92s3CYJb61ftNcnqMlgYZ9vy4zLIdovAOtcaFySJkGmVVlldOQ8ba+5NA5dQmXvoEeTb7tswHfTARV15bSvTpIPRtEMGASwaoz2KaJ2vS8hRHbidPLcnzp8Us1P2xQ5zMITnlNtDyfpTnpPwfyLhPUlvjhxYHNF5PjyS9qZd/Mn20teNgXVdbAtsCC6c9RaVjqF1BqyHArvSgK1goYviWmd3V029No3f7h3tsVd7aNed72kFJ+5043Glq3DIYsmZIrHgkvGEyWgMF5GKaBwzwjmVkoZCjSGiLI4jSVQSJkwwSqPR+O+kF0hFGdImXAmFNFQibcgxGmFMGI24EImMwjGIEAsVEywYS6RUo7T6MT3E54Ud/rqdC8lpSCVJGJUMBUuGBwsec8UlCbmSVAiGfsJIxbFSRFCG2wWVr9uJVRJTRhRH/wpb1dmJGMNGMSI4l6HkIhTYJtGdRQmLhYgiGfMnO4dMm8qjFYN3iikAXx+nO62OskP2O3dx+d3p27djArsSDgmZnGo/DcdwOILL+ZlsjOFGF8705gHube5XE+Bd9ZBWD30uj4L6/yXxN0nCbn7px9RR8+AdA33TvQ8BzmB+chwWzvivtjR16x9P3Kk88yT7sff87T5gRCmlo+lgPEgH0w67/wHMnN8WZt4XAO9tua4bD21TDAkJvMHJiRfugus2uzOeZM6Npo/I4Bg6y+0GbH55ZiBCVmjn8J+btiiW9pdJB/NZgPtfQIta57a6/bwxTaG33bYVm3/qPxJCZgGW55G+rvFqmmfMfwA