-
-
Notifications
You must be signed in to change notification settings - Fork 425
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
MTA:SA Server v1.5.6-r14489-release crash report #652
Comments
Try using build from https://linux.mtasa.com/ |
@ccw808 already created request to update binaries on hosting... and i also was thinking that it could be related to Matrixes crash, fixed not so long ago. But i'm not using matrixes on server side, only on client. And also it is not explaining the first crash accident on 1.5.5 ver. Meanwhile, server without players stands for more then 20 minutes so far. So it is happened due to some in-game situation. Is it possible to get any info from dump, so i can narrow the search? |
Looks like a crash in getElementMatrix with a ped element |
@ccw808 so, it means that r14493 will fix the issue on 1.5.6. But what caused initial crash on 1.5.5 then?...(( |
Last crash was fixed by update, but reason of the first one is unknow, so will close ticket for now. |
Describe the bug
At first crash appeared today at v1.5.5-11747 version, after more than 3 months of runtime. After first crash, i updated server to 1.5.6, all the resources and db's remain the same as before the crash, i started server and its crashed just after 15 minutes. I tried one more time, result was the same. The dump files in attachment.
Crash.zip
Version
Additional context
I have other servers which are running exactly the same resources but still on 1.5.5 ver of server. The only difference between them - is the players progress (database) So probably this could be related to same in-game situation with some script. There are plenty of them, so i have no idea where to look. This is the first incident during last 5 years. Last resources update was at July. 6 more servers are still running with same resources since July, without restarts. I hope somebody could suggest where to look, based on crash dumps.
The text was updated successfully, but these errors were encountered: