27.01.2012, 15:55
Hm, probably a plugin problem, or problematic plugin usage.
Scriptwise only playervariables could cause such a ram increase, or recursive functions (functions calling themselves and so looping again and again). You should check for these, but they are quite improbable, as playervariables are deletd when the player leaves, and recursive functions would rather make your server crash or lag like hell.
MapAndreas, sscanf and Whirlpool should be fine, as they all do not assign a lot of memory, and for MapAndreas ive never heard of or experienced such a problem.
Regex? Havent used it, or looked at its source yet, but it also shouldnt assign much ram.
Same for crashdetect and mysql.
So I guess the problem could most likely be the streamer, as streamers need lots of memory assignments when new objects are added. Maybe you are creating an unlimited amount of objects as a result of some buggy loadHouses() or loadMap()-like things.
Hard to say how to check it, as the problem could be anywhere in your script, or even in the plugin itself. Trying to debug problematic script parts like the objectloaders and waiting for someone else who had the same problem is probably the best.
Scriptwise only playervariables could cause such a ram increase, or recursive functions (functions calling themselves and so looping again and again). You should check for these, but they are quite improbable, as playervariables are deletd when the player leaves, and recursive functions would rather make your server crash or lag like hell.
MapAndreas, sscanf and Whirlpool should be fine, as they all do not assign a lot of memory, and for MapAndreas ive never heard of or experienced such a problem.
Regex? Havent used it, or looked at its source yet, but it also shouldnt assign much ram.
Same for crashdetect and mysql.
So I guess the problem could most likely be the streamer, as streamers need lots of memory assignments when new objects are added. Maybe you are creating an unlimited amount of objects as a result of some buggy loadHouses() or loadMap()-like things.
Hard to say how to check it, as the problem could be anywhere in your script, or even in the plugin itself. Trying to debug problematic script parts like the objectloaders and waiting for someone else who had the same problem is probably the best.