Skip to content

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

Closed
1 task done
haron4igg opened this issue May 6, 2025 · 6 comments
Closed
1 task done

Crash 0x00012AE8 #4202

haron4igg opened this issue May 6, 2025 · 6 comments
Labels
bug Something isn't working

Comments

@haron4igg
Copy link

Describe the bug

Hi! Discovered one crash, i assume this is one happens pretty often now to my players (approx last month)

Version = 1.6-release-23183.0.000
Time = Tue May  6 14:39:34 2025
Module = C:\Games\NS-DayZ\Multi Theft Auto1.6\mta\game_sa.dll
Code = 0xC0000005
Offset = 0x00012AE8

EAX=B12A1588  EBX=25581198  ECX=B12A1588  EDX=25581198  ESI=00000022
EDI=00000000  EBP=0177FCA0  ESP=0177FC94  EIP=5AD22AE8  FLG=00010246
CS=0023   DS=002B  SS=002B  ES=002B   FS=0053  GS=002B

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:

  1. die during PvP / PvE (could be related to fire )
  2. few seconds after respawn you crash

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

  • I have read and understood the Security Policy and this issue is not security related.
@haron4igg haron4igg added the bug Something isn't working label May 6, 2025
@haron4igg
Copy link
Author

haron4igg commented May 6, 2025

Image

Currently crash rate for this and #4204 is ~7%-10% of total connections, normal for us 3% :)

@haron4igg
Copy link
Author

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.

@PlatinMTA
Copy link
Contributor

Currently crash rate for this and #4204 is ~7%-10% of total connections, normal for us 3% :)

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?

@haron4igg
Copy link
Author

haron4igg commented May 6, 2025

i'm saving file with current version and some 'debug' info on client, refreshing it once per few seconds.
If user disconnect normaly - on resource stop i'm deleting file.
if file is present on login - i would assume it was crash. and then it will be reported, so i can collect crash statistics if people rejoin.
I also have top players who suffer crashes by serial, if it could be somehow useful (normally contacting them and askinng for help with investigations)

p.s. it is graylog just in case.

@Dutchman101
Copy link
Member

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!

@Dutchman101
Copy link
Member

Dutchman101 commented May 7, 2025

Fixed in PR #4206 & #4208
Thanks for reporting!

(New builds will be coming up and automatically sent to affected users)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants