PDA

View Full Version : Malloc issue.


Puppetmaster
04-24-2016, 20:56
Hello again everyone ;)

I am having a bit of an issue where ever since the latest csgo update my server has been unable to malloc memory at random times which freezes the server (and requires a sigkill to stop).

srcds_linux: malloc.c:3695: _int_malloc: Assertion `(unsigned long) (size) >= (unsigned long) (nb)' failed.and
*** Error in `./srcds_linux': free(): invalid pointer: 0x0dfafbc8 ***
*** Error in `./srcds_linux': free(): invalid next size (fast): 0x0d8ec2f0 ***The issue is persisting through a full server wipe.

When I add -debug to the start line I get this:
debug.cmds:1: Error in sourced command file:
Cannot access memory at address 0xff8156f4My debug.log is equally useless:

----------------------------------------------
CRASH: Mon Apr 25 19:15:56 AEST 2016
Start Line: ./srcds_linux -game csgo -console -debug -maxplayers_override 12 +sv_pure 0 +game_type 0 +game_mode 1 +mapgroup mg_active +map de_dust2 +hostport 27045 -tickrate 128 -ip 125.63.48.174 +exec autoexec.cfg
[New LWP 32164]
[New LWP 32434]
[New LWP 32649]
[New LWP 32643]
[New LWP 889]
[New LWP 2238]
[New LWP 32373]
[New LWP 32378]
[New LWP 32663]
[New LWP 32372]
[New LWP 32217]
[New LWP 2328]
[New LWP 2327]
#0 0xf779a440 in ?? ()
End of Source crash report
----------------------------------------------

Puppetmaster
04-26-2016, 18:47
Accelerator gives this:

0 linux-gate.so + 0x440
1 libc-2.19.so + 0x7281a
2 libc-2.19.so + 0x162f30
3 libc-2.19.so + 0x15ea13
4 libc-2.19.so + 0x15ea13
5 libc-2.19.so + 0x74bcf
6 server.so + 0xcfc508
7 libc-2.19.so + 0x751c0
8 sourcemod.logic.so!CForward::Execute(int*, SourceMod::IForwardFilter*) [ForwardSys.cpp:303 + 0x13]
9 sourcemod.2.csgo.so!TimerSystem::GameFrame(bo ol) [TimerSys.cpp:241 + 0x1b]
10 0x1

Should I assume its an issue with sourcemod?

Neuro Toxin
04-27-2016, 19:22
Looks like a forward from gameframe.

Have you got anything that hooks it?

asherkin
04-28-2016, 02:48
Link. The. Crash. On. Throttle.

Puppetmaster
04-28-2016, 04:32
The latest CS:GO patch seems to have fixed it. Thanks for all the help guys :D