Server crash std::out_of_range: basic_string

crash

#1
Sending heartbeat to live-internal.fivem.net:30110
Connecting: VaiLFaLLeN
terminating with uncaught exception of type std::out_of_range: basic_string
Stacktrace:

/proc/self/maps:
4130a000-4133a000 rwxp 00000000 00:00 0
417c4000-417d4000 rwxp 00000000 00:00 0
a0bff300000-a0bff32f000 rw-p 00000000 00:00 0
ea74bf00000-ea74bf80000 rw-p 00000000 00:00 0
1cd3b0dae000-1cd3b0e00000 ---p 00000000 00:00 0
1cd3b0e00000-1cd3b0e03000 rw-p 00000000 00:00 0
1cd3b0e03000-1cd3b0e04000 ---p 00000000 00:00 0
1cd3b0e04000-1cd3b0e7f000 r-xp 00000000 00:00 0
1cd3b0e7f000-1cd3b8dae000 ---p 00000000 00:00 0
2dc545b80000-2dc545b83000 rw-p 00000000 00:00 0
31b666b00000-31b666b80000 rw-p 00000000 00:00 0
34c07dc80000-34c07dd00000 rw-p 00000000 00:00 0
362a68f00000-362a68f03000 rw-p 00000000 00:00 0
362a68f03000-362a68f80000 r--p 00000000 00:00 0
3da5c0850000-3da5c0858000 rw-p 00000000 00:00 0
7f75cc2c6000-7f75cccee000 rw-p 00000000 00:00 0
7f75cccee000-7f75cccf0000 ---p 00000000 00:00 0
7f75cccf0000-7f75cd4f2000 rw-p 00000000 00:00 0
7f75cd4f2000-7f75cd4f4000 ---p 00000000 00:00 0
7f75cd4f4000-7f75cdcf6000 rw-p 00000000 00:00 0
7f75cdcf6000-7f75cdcf8000 ---p 00000000 00:00 0
7f75cdcf8000-7f75ce4fa000 rw-p 00000000 00:00 0
7f75ce4fa000-7f75ce4fc000 ---p 00000000 00:00 0
7f75ce4fc000-7f75ced3f000 rw-p 00000000 00:00 0
7f75ced3f000-7f75ced41000 ---p 00000000 00:00 0
Memory around native instruction pointer (0x7f75dab10f6f):
0x7f75dab10f5f  00 00 31 d2 bf 02 00 00 00 b8 0e 00 00 00 0f 05  ..1.............
0x7f75dab10f6f  c3 48 83 ec 08 48 63 ff b8 24 00 00 00 0f 05 48  .H...Hc..$.....H
0x7f75dab10f7f  89 c7 e8 0a 99 fd ff 5a c3 48 83 ec 08 48 63 ff  .......Z.H...Hc.
0x7f75dab10f8f  48 63 f6 b8 3e 00 00 00 0f 05 48 89 c7 e8 ef 98  Hc..>.....H.....

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

ddfa.sh: line 3:  2612 Aborted                 ../bin/run.sh +exec ddfa.cfg

If it’s a script error, what can it be? Can client send too long or malformed string that can kill server?


#2

:man_shrugging:

provide more information, these logs from Mono are literally useless.

basically, reproduce whatever issue on Windows or run a custom symbolic build in GDB


#3

i have the same problem all okay i only stop and started the Server now i have the same…


#4

I am now having this issue out of no where. Restarting both my FiveM server and VPS made no change. Running linux, was using a old build, and now tried with the newest FiveM Server build and its the same thing.

Not sure what other information you need to reproduce.

 terminating with uncaught exception of type std::out_of_range: basic_string
Jan 02 00:45:27 rusty-fivem-server2 sh[1382]: Stacktrace:
Jan 02 00:45:27 rusty-fivem-server2 sh[1382]: /proc/self/maps:
Jan 02 00:45:27 rusty-fivem-server2 sh[1382]: 41386000-414be000 rwxp 00000000 00:00 0
Jan 02 00:45:27 rusty-fivem-server2 sh[1382]: 4155f000-4164f000 rwxp 00000000 00:00 0
Jan 02 00:45:27 rusty-fivem-server2 sh[1382]: 417fb000-419ce000 rwxp 00000000 00:00 0
Jan 02 00:45:27 rusty-fivem-server2 sh[1382]: 41c94000-41ca4000 rwxp 00000000 00:00 0
Jan 02 00:45:27 rusty-fivem-server2 sh[1382]: 53c87389000-53c87400000 ---p 00000000 00:00 0
Jan 02 00:45:27 rusty-fivem-server2 sh[1382]: 53c87400000-53c87403000 rw-p 00000000 00:00 0
Jan 02 00:45:27 rusty-fivem-server2 sh[1382]: 53c87403000-53c87404000 ---p 00000000 00:00 0
Jan 02 00:45:27 rusty-fivem-server2 sh[1382]: 53c87404000-53c8747f000 r-xp 00000000 00:00 0

#5

It happened again.

561: license:5b0e79e62a660dc4475d15343ee6e22a9429d5f7
561: xbl:2535464008467545
561: live:1899947320263266
561: ip:23.127.226.39
attempting to load 561
loaded $0 and 0 garages
terminating with uncaught exception of type std::out_of_range: basic_string
Stacktrace:

/proc/self/maps:
40bf5000-40c05000 rwxp 00000000 00:00 0
41109000-41139000 rwxp 00000000 00:00 0
4cdac280000-4cdac283000 rw-p 00000000 00:00 0
4cdac283000-4cdac300000 r--p 00000000 00:00 0
1023fde00000-1023fde2f000 rw-p 00000000 00:00 0
146a01945000-146a01980000 ---p 00000000 00:00 0
146a01980000-146a01983000 rw-p 00000000 00:00 0
146a01983000-146a01984000 ---p 00000000 00:00 0
146a01984000-146a019ff000 r-xp 00000000 00:00 0
146a019ff000-146a09945000 ---p 00000000 00:00 0
170efc900000-170efc903000 rw-p 00000000 00:00 0
1d857be80000-1d857bf00000 rw-p 00000000 00:00 0
2ff1a0548000-2ff1a0550000 rw-p 00000000 00:00 0
37139f400000-37139f480000 rw-p 00000000 00:00 0
3c6ed9900000-3c6ed9980000 rw-p 00000000 00:00 0
7fd344f10000-7fd345875000 rw-p 00000000 00:00 0
7fd345875000-7fd345877000 ---p 00000000 00:00 0
7fd345877000-7fd346079000 rw-p 00000000 00:00 0
7fd346079000-7fd34607b000 ---p 00000000 00:00 0
7fd34607b000-7fd34687d000 rw-p 00000000 00:00 0
7fd34687d000-7fd34687f000 ---p 00000000 00:00 0
7fd34687f000-7fd347081000 rw-p 00000000 00:00 0
7fd347081000-7fd347083000 ---p 00000000 00:00 0
7fd347083000-7fd3478c6000 rw-p 00000000 00:00 0
7fd3478c6000-7fd3478c8000 ---p 00000000 00:00 0
Memory around native instruction pointer (0x7fd35369af6f):
0x7fd35369af5f  00 00 31 d2 bf 02 00 00 00 b8 0e 00 00 00 0f 05  ..1.............
0x7fd35369af6f  c3 48 83 ec 08 48 63 ff b8 24 00 00 00 0f 05 48  .H...Hc..$.....H
0x7fd35369af7f  89 c7 e8 0a 99 fd ff 5a c3 48 83 ec 08 48 63 ff  .......Z.H...Hc.
0x7fd35369af8f  48 63 f6 b8 3e 00 00 00 0f 05 48 89 c7 e8 ef 98  Hc..>.....H.....

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

ddfa.sh: line 3:   767 Aborted                 ../bin/run.sh +exec ddfa.cfg

I wonder what can it be, I didn’t change server scripts much and used build 934 for a week and suddenly it started crashing like this.


#6

As stated in the Discord, FiveM developers are working on the issue.

Cross-Post/Edit

This is a global issue at this time. there is no ETA for when the servers will be up again. The outage is beyond our/my control. this issue could last through to later in EU time.EU time.


#7

Sorry, didn’t know there was an announcement about it. Checked the forums but didnt think to check the discord


#8

No problem man, it took all of us by surprise.


#9

damn bruh thought it was zap hosting causing this shit.


#11

Fixed as of the following commit:


#12