Verse crash: ErrRuntime_ComputationLimitExceeded

Development Programming & Scripting Verse
, , , ,
1

I’ve been experiencing this crash for a while now. The stack trace provides no guidance on where the issue could be coming from. I’ve debugged the whole game with a full lobby and a tick rate graph multiple times, and I was never able to see any performance issues.

These crashes occur in batches: every once in a while, a bunch of instances pop up at the same time in my technical tab on the creator portal, then they disappear for days, even while maintaining similar levels of CCUs.

I would be grateful if anybody could give advice on how to overcome this issue, or at least find out where it’s coming from.

Here are the two stack traces I’m getting most of the time:

Verse unrecoverable error: ErrRuntime_ComputationLimitExceeded: The runtime terminated prematurely because Verse code took too long to execute within a single server tick. Try offloading heavy computation to async contexts. (Script (PersistentLevel_VerseContentScope) has exceeded its maximum running time. Possible infinite loop or excessive computation.) (Callstack unavailable)

Verse unrecoverable error: ErrRuntime_ComputationLimitExceeded: The runtime terminated prematurely because Verse code took too long to execute within a single server tick. Try offloading heavy computation to async contexts. (Script (PersistentLevel_VerseContentScope) has exceeded its maximum running time. Possible infinite loop or excessive computation.) Truncated callstack follows: Device->rigger_V2_C:ExecuteUbergraph?ice->rigger_V2 (Unknown source) (Source: Unknown(0,0, 0,0)) Device->rigger_V2_C:BroadcastActivateTrigger (Unknown source) (Source: Unknown(0,0, 0,0))

1 Like
2

If you’re still having this issue, could you please post in Issues and Bug Reporting - Epic Developer Community Forums with all of your latest information? Thank you!

3

The error basically means that something called from Verse code is taking too long and has stalled the server.

There are two common causes:

  • Your code has some intensive or infinite inner loops. It doesn’t sound like you have an infinite loop here, if it sometimes works, but is it doing too much work (like, many thousands of complex operations per frame)? Perhaps something on startup?
  • You’re trying to load something very big & expensive (textures, meshes, …) from Verse. That path still needs optimising and you can stall things if you’re not careful.

To try and narrow it down, you could print which step it’s getting to? Sorry I can’t be more help without actually seeing the project.