-
-
Notifications
You must be signed in to change notification settings - Fork 460
Crash 0x00012AE8 #4202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Currently crash rate for this and #4204 is ~7%-10% of total connections, normal for us 3% :) |
Also we noticed, and players as well, that when you try to rejoin game after crash - first time mta will crash (close) without any message. |
offtopic but i love those graphs im pretty sure you made an issue using them before, how do you count the crashes? do you ask the client on re-connect after a Timed Out if they crashed or you just assume every Timed Out is a crash? |
i'm saving file with current version and some 'debug' info on client, refreshing it once per few seconds. p.s. it is graylog just in case. |
I can confirm that this is a new bug, and the popularity of crash is quite high already. It must've been introduced with the builds that gone into circulation last week, and it can happen randomly. As first step i forwarded the technical details of this crash to a couple of devs. It's likely that someone fixes it in the coming 24 hours. Thanks for reporting! |
Describe the bug
Hi! Discovered one crash, i assume this is one happens pretty often now to my players (approx last month)
client_1.6-release-23183.0.000_gamesa_00012ae8_5_CGNM_C269DE53_55F3_0F8_A6EA6_20250506_1439.rsa.dmp
Steps to reproduce
From what i heard from player and way i reproduced it:
probably related to 'streaming out' after respawn.
I managed to reproduce it by repsawning at place of death and flying away immideately.
when normaly players respawn far away from death place.
If someone could check crash-dump and tell me to what its releated, i could get more insight.
Version
Version = 1.6-release-23183.0.000
Additional context
No response
Relevant log output
Security Policy
The text was updated successfully, but these errors were encountered: