Maniaplanet Forum

looks like the only way how we get any attention to that is shutting down our servers at the same time for a week or some other action that everybody see. Or does somebody have a better idea?
wasting more than 20 gb ram for some TM2S servers are.... not nice for me.

or does somebody have a better idea?

By the way, if I remember correctly this crash bug wasn't on Canyon beta, because my server was very successful there, I had many times arround 100 players, and the server never crashed.

nocturne wrote: In the meantime, we all go crazy..

Yep.

TheBigG. wrote:looks like the only way how we get any attention to that is shutting down our servers at the same time for a week or some other action that everybody see. Or does somebody have a better idea?
wasting more than 20 gb ram for some TM2S servers are.... not nice for me.

or does somebody have a better idea?

I do not think that this will help anything. Players will just join other servers...

killer606 wrote:By the way, if I remember correctly this crash bug wasn't on Canyon beta, because my server was very successful there, I had many times arround 100 players, and the server never crashed.

Nope, prooved it. Currently the Bug also occures in TMCanyon. This might have changed since the Beta of TMcanyon so that the memleak propably has been kinda "added" ( ) in the "last" time. And with that I mean within the last 3 months.

@nocture: I also agree with you that this is not a too complex problem, they are just our of human resources I think. BUT if they really fixed it and did not release it yet for any reason, it would be nice to have a little notice right here that says "we've done it, its goign to be released in a month..."

Bueddl wrote:

killer606 wrote:By the way, if I remember correctly this crash bug wasn't on Canyon beta, because my server was very successful there, I had many times arround 100 players, and the server never crashed.

Nope, prooved it. Currently the Bug also occures in TMCanyon. This might have changed since the Beta of TMcanyon so that the memleak propably has been kinda "added" ( ) in the "last" time. And with that I mean within the last 3 months.

Actually, we had a mem leak in TMCanyon at release too.. Just look at the beta server thread, which we were forced to use for months and months after the retail release, for my constant whining about it for the first 6 months of it's release before I just abandoned hosting/developing for TMCanyon altogether. If you host on windows, congrats.. no mem leak (though who hosts on windows servers anyways..? lol).

Can't help but think since it seems it was eventually fixed on Canyon, they probably already know what the exact problem is and exactly how to fix it.

C'mon guys.. really want to buy this game (as well as being able to recommend it to all our TMF players that left after the FreeZone fiasco) -- after all, it's just a few bucks. Just don't want to waste more money on a game that'll take months to fix, let alone promote it if I'll be forced to abandon it yet again.

TheBigG. wrote:looks like the only way how we get any attention to that is shutting down our servers at the same time for a week or some other action that everybody see. Or does somebody have a better idea?
wasting more than 20 gb ram for some TM2S servers are.... not nice for me.

or does somebody have a better idea?

That's about the same as those organized efforts to protest gas prices by not buying gas on a certain date.. You're still going to drive the same, and just buy more gas the day before. Not a whole lot we can do, besides shaming Nadeo into eventually fixing it (hasn't worked so far); or perhaps demand your money back if you've already paid for the game or even deny credit card payment for the game (though the distributors like Steam are likely the only ones to suffer). Wonder how Ubisoft would feel about all of this..

FWIW, can submit support tickets on the main Ubisoft website for TMCanyon and TMStadium..

There seems to be another memory issue.
We had that now 4 times, that a totally empty server allocated about 2GB of RAM in less than 5 minutes and freed it in the same length of time afterwards.

See here:
http://i.imgur.com/ZKMGWfX.png

I Know I will bee shouted a0,t but my server uses a steady 150mb I don't have a lot of players rarely more then 5 and they don't stay for very long but still they have been runing for nearly a month now and there hasn't been an increase.

It misht just be the low player count on my server don't know

oliverde8 wrote:I Know I will bee shouted a0,t but my server uses a steady 150mb I don't have a lot of players rarely more then 5 and they don't stay for very long but still they have been runing for nearly a month now and there hasn't been an increase.

It misht just be the low player count on my server don't know

Yes this seems to be because of the low player count. When looking at the graphs you cansee that the first memory allocated is at 10-15 players. I think the dedicated server offers at startup enough ram to host for that player amount and if it goes upon that value it takes more memory.

Thats what I am seeing when analysing the collected data. So this may have its reson in this

I think it's important to know what operating system each of you are running your servers on to see if these memory problems are linked to the code on a particular platform.

For example. I'll list the server info for my own. (Mine happen to be taking between 250-350MB each)

=======================

OS: Windows XP Professional SP3

Server #1:
Title: ShootMania Storm
Max Players: 16
Script (if applicable): TeamFNG_Royal.Script.txt (the latest Royal script before it was moved into the Royal title pack, tweaked)
Mode (if applicable): N/A

Server #2:
Title: TrackMania 2 Stadium
Max Players: 50
Script (if applicable): N/A
Mode (if applicable): Time Attack

Server #3:
Title: TrackMania 2 Canyon
Max Players: 50
Script (if applicable): N/A
Mode (if applicable): Time Attack

=======================

Hope this will help.

I think the rest of us is using Linux. In my case GNU/Linux Debian 6.0, 64-Bit.
I don't think it is bound to the game mode, but each uses TimeAttack.

But hornestly I do not think that at this time is anyone of NADEO reading that topic. At least not xbx who is responsible for this.

fng_thatoneguy wrote:I think it's important to know what operating system each of you are running your servers on to see if these memory problems are linked to the code on a particular platform.

For example. I'll list the server info for my own. (Mine happen to be taking between 250-350MB each). . .OS: Windows XP Professional SP3...

As far I've been able to tell, the memleak is only prevalent in *nix servers, though 250-350mb apiece seems like a bit much (besides the SMStorm server -- FPS servers involve much more processing). In Win8 x64, any test server I've set up barely gets past 90mb. Why are you still on XP btw..? Horribly outdated security and performance wise.. I charge an extra $15 an hour just to work on XP boxes for clients, hehe.

In my case, server is running Centos6 x86_64 -- the most popular enterprise/server operating system out there.