Summary
On a couple of our maps, we are randomly seeing a new Verse runtime error. This error initially occurred 6 days ago for both maps. The error occurred a handful of times (2/12) and then stopped occurring.
The common part of the error message is:
Verse unrecoverable error: ErrRuntime_MemoryLimitExceeded: Exceeded memory limit(s). (Ran out of memory for allocating UObjects while attempting to create a Verse task:
The stack traces referenced by the crash message are confusing if the crash was caused by running out of memory for allocating UObjects.
One stack trace references calling Sleep(), the other stack trace references OnExit() for a volume.
Is there a chance these errors were induced by some change on the back end? If not, is it possible to get a clue as to what causes this type of crash? If this crash was truly being induced by an issue in the map, I would expect to see MANY more occurrences of this error. The volume OnExit event being referenced is a core aspect of the gameplay loop for a map with 1k+ CCU
Please select what you are reporting on:
Verse
What Type of Bug are you experiencing?
Stability
Steps to Reproduce
UNKNOWN
Expected Result
Do not have intermittent crashes in reference to UObject memory allocation while creating a Verse task.
Observed Result
Crashes in reference to UObject memory allocation while creating a Verse task.
Platform(s)
UNKNOWN
Additional Notes
It did not seem like these runtime errors were immediately raised to the Content Service. In general I check the runtime errors every day, so I was surprised to see a NEW error with the first occurrence listed as happening 6 days ago. This is what makes me suspect this is either a new type of runtime error being raised to the content service, or was potentially induced on Epics end. The infrequency of the occurrences further supports this conclusion.
