10.01.2015, 09:03
Okay guys, so I'm having this issue with YCMD. Each time I type certain commands, or enter them wrongly, my server crashes. Here's the error;
This message continuously spams itself, after a few minutes of nobody being on the server it stops.
Additionally, all the other commands including the command I entered incorrectly in-game would stop working (Server: Unknown Command Error) until I restart the server.
I would like to know if there is a fix so this can be prevented from happening when I do eventually launch..
Код:
[17:54:19] [debug] AMX backtrace: [17:54:19] [debug] #0 00000008 in public CheckBasketBall () from ALRP.amx [17:54:19] [debug] Run time error 8: "Heap underflow" [17:54:19] [debug] Heap pointer (HEA) is 0x18FDF8, heap bottom (HLW) is 0x6FE4A0 [17:54:19] [debug] AMX backtrace: [17:54:19] [debug] #0 00000008 in public GUISpeed () from ALRP.amx [17:54:19] [debug] Run time error 8: "Heap underflow" [17:54:19] [debug] Heap pointer (HEA) is 0x18FDF8, heap bottom (HLW) is 0x6FE4A0 [17:54:19] [debug] AMX backtrace: [17:54:19] [debug] #0 00000008 in public SeatBeltTimer () from ALRP.amx [17:54:20] [debug] Run time error 8: "Heap underflow" [17:54:20] [debug] Heap pointer (HEA) is 0x18FDF8, heap bottom (HLW) is 0x6FE4A0 [17:54:20] [debug] AMX backtrace: [17:54:20] [debug] #0 00000008 in public GUISpeed () from ALRP.amx [17:54:20] [debug] Run time error 8: "Heap underflow" [17:54:20] [debug] Heap pointer (HEA) is 0x18FDF8, heap bottom (HLW) is 0x6FE4A0 [17:54:20] [debug] AMX backtrace: [17:54:20] [debug] #0 00000008 in public SystemTimer () from ALRP.amx [17:54:20] [debug] Run time error 8: "Heap underflow" [17:54:20] [debug] Heap pointer (HEA) is 0x18FDF8, heap bottom (HLW) is 0x6FE4A0 [17:54:20] [debug] AMX backtrace: [17:54:20] [debug] #0 00000008 in public SeatBeltTimer () from ALRP.amx
Additionally, all the other commands including the command I entered incorrectly in-game would stop working (Server: Unknown Command Error) until I restart the server.
I would like to know if there is a fix so this can be prevented from happening when I do eventually launch..