You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a hotspot for crashes between Valentine and Flatneck station.
Our research shows that it is not a script or MLO related crash, as it happens on a clean server with no resources.
Over the past few days, we have gathered crashdata and have a realtime map with hotspots related to this area, which can be easily reproduced by just running into this area.
The crash leaves no crashdump, the client just freezes.
On the server, the client will have timed out.
Server->client connection timed out. Last seen 36198 msec ago.
Expected result
The client should not have crashed.
Reproduction steps
Connect to a server, with or without resources
Go to the intersection close to the hotspot as shown on the image above, and run towards the hotspot
The client will freeze, and after a few seconds, the client will have timed out on the server
Importancy
Crash
Area(s)
RedM
Specific version(s)
RedM 1491.50
Additional information
No response
The text was updated successfully, but these errors were encountered:
What happened?
There is a hotspot for crashes between Valentine and Flatneck station.
Our research shows that it is not a script or MLO related crash, as it happens on a clean server with no resources.
Over the past few days, we have gathered crashdata and have a realtime map with hotspots related to this area, which can be easily reproduced by just running into this area.
The crash leaves no crashdump, the client just freezes.
On the server, the client will have timed out.
Server->client connection timed out. Last seen 36198 msec ago.
Expected result
The client should not have crashed.
Reproduction steps
Importancy
Crash
Area(s)
RedM
Specific version(s)
RedM 1491.50
Additional information
No response
The text was updated successfully, but these errors were encountered: