Everytime I connect to my server, I get an Assertion-Error (see Screenshots below).
Client
Windows version:
Windows 10 Pro, Version 1809
System specifications:
i5 6600
Zotac GTX 1080 Amp Extreme Edition
16GB RAM
installed on HDD
Server
Operating system:
Same as Client (just a testserver)
System specifications:
Same as Client (just a testserver)
Artifact version:
1208 and a few others down to 1190
IP address:
localhost
Resources:
- FiveM default resources
- custom Framework (which is in development right now / unfinished)
- custom loadingscreen
- mysql-async
- bob74_ipl
- vSync
- NativeUI
- StreetLabel
- Speedometer
- custom WeaponMeta Streaming
(the error also happens without non-default resources)
Incident
Summary:
Server starts without any error. Any user connecting results in an immediate crash of the Server.
Expected behavior:
Server not crashing at all.
Actual behavior:
Server crashes with an Assertion Error
Steps to reproduce:
- Start Server
- let any client connect
- server crash
Server/Client?
Server Crash
Error screenshot (if any):
Server Error (red is the custom frameworks’ name, don’t want people to know it yet)
Client Error (of course when the server crashes it fails to connect)
.dmp files/report IDs:
Crash report ID: be535d8a-80dc-4825-8066-f63c7bda541b
817b303c-97f1-445c-befe-c9134104db51.dmp (1.2 MB)
Any additional info:
It used to work without any problem before I started updating to the newest artifact version and of course this one time I didn’t make a backup, I would actually need it.
I will try a few older artifact versions and add them to this post if I get the same error again.
Further testing resulted in the same error.
But I found the solution somewhere else. Apparently I forgot to disable a single resource (mysql-async) while testing. After deactivating that resource, everything is working as intended again.
An update of mysql-async also fixed the error and everything is running fine again!
