Hi there, I am an editor at Dutch-news outlet Bellingcat, contacting you on behalf of multiple major European publishers including Dei Zeit, Der Standard, Le Monde, RFI, Forbidden Stories.
Together we published stories this morning which included a 3D model created via Cesium.
Not long after publishing, at approx 9:15am CET, Cesium crashed and none of the models loaded nor could we open Cesium site.
The Cesium models are back up and working now. But it’s critical we don’t have this error again as major publishers have included Cesium model in our work.
Who is the Cesium contact we can keep in touch with about this important matter throughout the course of today and beyond?
Can someone from Cesium message me directly with your contact details so that we can keep in touch on this important issue.
Thanks for this report!
There has been a short, temporary spike in the response times for certain Cesium ion services. Right now, all services should be up and running with normal performance again.
The service health and response times are constantly tracked internally. The quickest way to make us aware of other issues (like degraded performance in certain geographical areas that may not be detected immediately) is here in the forum, or a mail at support@cesium.com.
The details of what caused these spikes in the response times are currently investigated. They may be related to a cloud service provider, or a change in certain database access patterns. Details and further information about the reasons, and plans to mitigate such delays in the future, will be published here as soon as possible.
bye
Marco
Hi @Marco13, this is Logan, a developer who has worked with Lucy and Bellingcat on this story. We’re also experiencing crashes in this story on certain older phones. I assume this is an issue related to available video memory. Is there any way to resolve this within Cesium?
Thanks!
Logan
@Logan_Williams This seems to be unrelated to the original topic of this thread. It might be best to open a new thread about this in the CesiumJS section, with all the details that might be relevant here. For example, the exact devices where the crash appears, maybe some information about the type and structure of the data, specific conditions or user actions that cause the crash, and the exact error message and maybe the stack trace. This would allow to keep things focussed and dedicatedly handle the issue that you mentioned.
Okay, I have made a new thread referencing this one. Can you assist now?
I cannot reproduce the issue due to lack of Mobile/Safari environment, and the description until now probably does not contain enough information to analyze the issue. But I’ll tag the CesiumJS core team, hopefully someone can ask the right questions or provide further assistence there.