Twice today, following the 171231 update, and successive masterlist fail to list, I’ve seen india-winter-beryllium strip my favorite server 446 of every player from 18 to 0, and six hours later from 13 to 0, and never ever before this.
This is an awkward one. There’s usually no reports on any given day, however some days the report count increases to 20-30 - but it’s only happened a total of ~600 times over the course of the past few months.
CPed+4328d being null during handling of (presumably received?) clone sync data. Adding it to the bucket of ‘uncommon crashes caused by data corruption’.
17 people were killed today in yet another senseless India-winter-beryllium mass murder. The killer or killers remain at-large, and should be considered only active on busy servers.
The mass-murderer known only as India-winter-beryllium has struck again, but this time completely differently. I was the only crash and while FiveM client was idle and minimized for over an hour. All other players were unaffected, escaping this certain tragedy unscathed.
I’m thinking it might be time to drop the uncommon from this forum tag: “crash memory-corruption uncommon” It is apparently quite common. Hitting me 6 times in 3 weeks, killing 82 players.
An observation from someone who runs a lot of mps and has seen all the systemic unsolvable errors hell can create for our ego’s to inevitably triumph over or workaround… this one is regular but not reoccurring. Once it has happened that is it for the day. This, if correct, and not just the assumption of short term data, would indicate that whatever causes the error is solved by the error. And it seems equally likely that it is the result of an accumulation of issues rather than an infrequently accessed single trigger mechanism.
The errors accumulate until triggering this mass error India-winter-beryllium, in a ‘straw that breaks the camel’s back’ manner, crashing every client, and not again for quite some time, because each new trigger is just one more piece of straw. That is my guess… so far. Like some sync cache is stored and stored instead of being sent and sent, stored until it floods then ultimately released. Or some similar stacking up mechanism to that. Just a guess.
Though delta-red-lithium appears less common than india-winter-berylium I am reasonably convinced they are the same error. Here again. Slughtering the server, all clients crash. Recorded in crash and logs from two instances of the same error. 10 dead, 5 wounded.