MEMORY LEAK DETECTED IN PLUGIN r682

cmer · **Author**

Hello,

After update too version r682 crash log

Code:

L 05/28/2012 - 19:56:05: [SM] MEMORY LEAK DETECTED IN PLUGIN (file "zombiereloaded.smx")
L 05/28/2012 - 19:56:05: [SM] Unloading plugin to free 15204 handles.
L 05/28/2012 - 19:56:05: [SM] Contact the author(s) of this plugin to correct this error.
./srcds_run: line 372: 11475 Segmentation fault      $HL_CMD
Add "-debug" to the ./srcds_run command line to generate a debug.log to help with solving this problem
Mon May 28 19:56:05 CEST 2012: Server restart in 10 seconds
Running a benchmark to measure system clock frequency...

hoping that this might help you

rhelgeby · *Last edited by rhelgeby; 05-29-2012 at 13:33.*

Yeah I suspected that, but wasn't able to trigger it myself. At least now it's confirmed. Thanks for testing.

How long did it last before SM detected a leak? Hours? days?

Perhaps you could try an older snapshot, like r678? This is the one where we started to use new features in the cstrike extension. If it's fine it will reduce the amount of revisions that I need to investigate too.

At least now the difficult debugging starts. If others want to investigate (I suppose not

) it's somewhere between r675 and r682. Most likely something was broken from r680 (inclusive).

cmer · 05-29-2012 , 15:12 Re: MEMORY LEAK DETECTED IN PLUGIN r682

New :p

Code:

L 05/29/2012 - 20:44:43: [SM] MEMORY LEAK DETECTED IN PLUGIN (file "zombiereloaded.smx")
L 05/29/2012 - 20:44:43: [SM] Unloading plugin to free 15257 handles.
L 05/29/2012 - 20:44:43: [SM] Contact the author(s) of this plugin to correct this error.
./srcds_run: line 372: 31463 Segmentation fault      $HL_CMD
Add "-debug" to the ./srcds_run command line to generate a debug.log to help with solving this problem
Tue May 29 20:44:43 CEST 2012: Server restart in 10 seconds

Uptime server: 2 hours
Players: 42

New version install r678 no probleme for moment

rhelgeby · *Last edited by rhelgeby; 05-29-2012 at 16:45.*

As short as two hours? Then I might be able to trigger it myself with bots I hope.

If r678 seems to be fine after a few hours with lots of players you could try r680. That one is in the "middle" and there will be 50% less snapshots to test every iteration and a lot less code changes to investigate.

Update: The leak might to be related to a timer and map changes. I suspect this change broke it: http://www.helgeby.net/zrdev/hg/hgwe.../zr/infect.inc (the changes in InfectOnMapStart). The timers doesn't last through map changes (at least they shouldn't) and the handles become invalid, so I just reset them. I don't remember if this is correct or not. But this change also exist in the latest official patch, so I'm not sure. If this really is the cause I'm surprised that no one have reported it.

rhelgeby · 05-29-2012 , 17:47 Re: MEMORY LEAK DETECTED IN PLUGIN r682

Possible fix: r683 - changeset

Try this for a few days. I don't know if it's actually fixed, but hopefully it is.

daleGEND · 05-30-2012 , 08:17 Re: MEMORY LEAK DETECTED IN PLUGIN r682

Quote:

Originally Posted by rhelgeby

Possible fix: r683 - changeset

Try this for a few days. I don't know if it's actually fixed, but hopefully it is.

Good stuff, i love fixes lol.

rhelgeby · *Last edited by rhelgeby; 06-10-2012 at 09:37.*

Update: New official patch in release thread: http://forums.alliedmods.net/showthread.php?t=111492

----

Another fix: r685 - changeset

This time it's a fix for sure, but it's best if a few people test its stability before I make it official.