Crash on Quest 2 / Quest 3 after around 20 minutes of playtime

Cesium for Unity
1

Cesium for Unity 1.7.1.

16 people using a quest vr device (android) experienced this exact crash on their own device atleast once:

Abort Reason: terminating (libCesiumForUnityNative-Runtime.so)

2

Hi @Your_RainBoy ,

Nothing in that callstack jumps out at me, but based on your description of “Crash after 20 mins” by multiple users, it does lead me to suspect running out of memory.

Reinforcing that, we do have an open issue related to memory leaks, link

How many and what kind of tilesets are in your scene? Are you using Google P3DT tiles?

Thanks

3

indeed, i am using P3DT tiles, i have 336870912 allocated bytes in the faulty scene,
i optimized some scripts and updated some packages and the crash seems to occur more rarely than before, i also found that i had Incremental Garbage Collector TURNED OFF. which i turned on right after.
i will update you on this tommorow or the day after.

4

See also the related GitHub issue here:

5

As I’ve specified on GitHub, this is NOT an ‘out of memory’ or low storage space crash, there is 1gb+ of free allocated memory available at all times, even during the crash. And storage has a lot of free space.

Call stack: Crash on Quest 2 / Quest 3 after around 20 minutes of playtime · Issue #408 · CesiumGS/cesium-unity · GitHub

v1.12.0 Cesium for Unity

v1.7.1 (currently used version) returns the same crash type.

Unity 2023.1.0f1

6

New info:

The crash apparently only occurs ONCE in no more than 30 minutes.

Then no matter how intensive or long play sessions last, it doesn’t crash again.

However, I think this resets on rebooting the device or updating the app.

Again, it’s not an out of memory crash, nor storage space limitation.

Lastly, the one-time crash could sometimes not occur at all, not even once, but more debugging is needed..