SCG Banner
Today's events : =Friday Night Gaming= Team Fortress 2
icon
Unknown Account
This post is not tied to an account, it may be from before the JB
Discussion: Memory Leak on Boysenberry? posted in Archives

I just logged on again when there was only one other player (KierDran), and the server was lagging significantly. Since I don't really have any machines running (just a couple solar panels hooked up to a storage unit, which stopped because the unit got full anyways), this leads to 3 possibilities, I think.

1.) KierDran alone is able to cause the lag somehow. Though, I doubt this is the case since KierDran has been on before with other people and there wasn't any lag (unless they're doing something really intense right now).

2.) There are a lot of World Anchors keeping a ton of machines active. Again, I doubt this is the case as it takes ~13 World Anchors spread out just to keep the same number of chunks active as a single player, and this would also cause constant lag all the time, even when the server is full, which we don't see happening since the server often runs just fine.

3.) There is a memory leak somewhere that builds and builds and builds over time. I think this may be the case because it is independent of how many players/machines are on and is consistent with the symptoms we're seeing. Needing to restart the server once a day because it lags after so much time passes, whether or not it's in large use, points to a memory leak. I don't know where the memory leak might be, since quick searches to see if Tekkit has any reported memory leaks has proven fruitless, but it might be worth looking into.

I'm sure that people have mentioned a memory leak before, but I recall Rowdy or Hera saying it was simply due to the machines people have going. But if it was the machines, the lag would be more constant and consistent. Unless you mean there's a memory leak with the machines, in which case do we know which machines or processes have the leak, since it could be reported to the Tekkit forums?

Last edited : by Administration

This discussion has no replies...yet.