Mango-Xray-Wyoming

RedM Discussion RedM OneSync reports
1

This specific crash has been fairly present throughout all of our time running OneSync. It has persisted all the way from roughly around the OneSync Tech Preview start, to current.

Repro Steps are a little hit or miss, but essentially: Frequent travel across the map removing, and adding players (OneSync culling itself, no scripts running touching this) will eventually trigger a Mango-Xray-Wyoming crash.

Currently we are enforcing DLC 1436, running Artifacts 4933, and I have no data on if this occurs less on Canary, but it is very common on Production.

CfxCrashDump_2021_11_05_03_56_51.zip (2.2 MB)

2

Updating with some dmps from players

I’m told these are also Mango-Xray-Wyoming

235d18e3-04fc-4999-ae19-b256475f01ec.dmp (9.1 MB)

38f70ac1-af7c-4132-9128-c311e782dc9d.dmp (9.2 MB)
75811756-9e06-4a57-a597-4284fcef478f.dmp (379.5 KB)
a5ec6e2a-83d1-4ab6-bbc1-a6447033472a.dmp (9.1 MB)
2ed0dfeb-8f6b-444a-9c8a-5dc0e4f37e56.dmp (382.1 KB)

3

Some additionals from today - we have updated to Artifacts 4939 - User is on Prod (These are definitely Mango Xray Wyoming, came from a staff member rather than users like the middle post)

CfxCrashDump_2021_11_08_01_06_30.zip (2.3 MB)
CfxCrashDump_2021_11_08_01_09_19.zip (2.2 MB)

4

Additional on my client from this morning:

46a4f725-d3cf-4406-b440-ef59e4102d51.dmp (9.0 MB)

5

Additional today while leaving Valentine (large group of players there)

67c64af5-ae2d-4e3b-bdc2-baf70ab6e467.dmp (9.2 MB)