Visual C++ Crash

Hi,

sometimes my project crashes with the follwing message:

This application has requested the runtime to terminate it in an unusual way

When this happens it crashes Unity at every startup, and I cannot work on the project anymore. I tried deleting the Library folder, even using another version, but still happens after the first crash.

It seems that this happens during a script reloading while compiling Cesium dll.

Using Unity 6 and Cesium 1.15.1

Thanks for the question @fra3point. In general, the more information you can give us about a crash - like the Unity log file - the easier it will be for us to help solve it. However, going off of other bug reports we’ve had recently, I have a suspicion that this might be related to some crashes in Unreal and Unity we’ve seen stemming from a bug in our glTF copyright parsing. We’ve pushed a hotfix for this issue - try updating to 1.15.3 and seeing if that fixes the crash. If not, the Unity log file or any other details you can find about the source of this crash would be a big help!

Thanks for your fast reply!

Sorry for not provideing enough information, I’ll try to add something:

The crash happened for the first time when I interrupted an Android build, and after the reload of scripts the message appeared. From that moment, every time I opened the scene, the crash happened, making my project unusable. Deleting some project folders like Library and Temp and restarting Unity, sometimes fixed the problem, but not always.

In the log file I don’t see anything relevant about this crash.

I’ve upgraded to the 1.15.3 version. I’ll make some more tests today trying to figure out if the issue is resolved or, otherwise, what causes the crash.

Thank you,
Francesco

We have a similar issue that just started popping up in not just our Unity projects, but also our existing, older Unity builds. As advised, we have tried to update our Cesium-unity package to 1.15.3, but that has so far been unsuccesful as we keep getting a deluge of errors involving the Reinterop namespace. We have tried several methods of adding the updated package but nothing seems to fix it.

Please see here for information about the Google Photorealistic 3D Tiles crash and how to upgrade Cesium for Unity to fix it:

@Boris, welcome to the community! Upgrading Cesium for Unity should be a relatively straightforward process within the Unity Package Manager. The link above has a little more detail, and the link to the Quickstart which has a lot more detail. Let us know if you’re still having trouble. Reinterop errors are usually the result of trying to using the GitHub repo directly as a Unity package (this won’t work), or perhaps indicate you just need to restart the Unity editor.

That seems to have done the trick; thank you!