• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

The Forgotten Server 1.1

Status
Not open for further replies.
Announcing the immediate availability of The Forgotten Server version 1.1.

The highlights of this release are:
  • Game protocol 10.77
  • Non-blocking SQL queries
  • Full utilization of creature and item userdata, with backwards compatibility in compat.lua
  • Extended item attribute customization
  • Improved XML error handling
This release has been brought to you by:
Changelog: https://github.com/otland/forgottenserver/wiki/Changelog-1.1
Download: https://github.com/otland/forgottenserver/releases/tag/v1.1
 
Click to expand...
Mark said:
64-bit uses twice as much memory for pointers, so it's probably still leaking in the 32-bit version, just that you have enough memory to live with it.
Click to expand...

Okay, but the memory is leaking like crazy with 64bit, while with the 32bit it dosen't leak at all.
I would agree if the 32bit showed something after and hour or two but it dosen't.
Is there an explanation for this?
 
What do you mean with memory leaking? You mean that the datapack uses extra much memory than it should?
 
WibbenZ said:
Okay, but the memory is leaking like crazy with 64bit, while with the 32bit it dosen't leak at all.
I would agree if the 32bit showed something after and hour or two but it dosen't.
Is there an explanation for this?
Click to expand...

Yes, semantics can differ over the two different architectures if the software is written to treat them differently.

Tarek1337 said:
What do you mean with memory leaking? You mean that the datapack uses extra much memory than it should?
Click to expand...

It means that the application doesn't return memory it no longer needs to the operating system.
 
WibbenZ said:
Okay, but the memory is leaking like crazy with 64bit, while with the 32bit it dosen't leak at all.
I would agree if the 32bit showed something after and hour or two but it dosen't.
Is there an explanation for this?
Click to expand...
The 32 bit survey much. I had my ORTS server online for 98 h i think. Then we did a restart. :p
 
Tarek1337 said:
The 32 bit survey much. I had my ORTS server online for 98 h i think. Then we did a restart. :p
Click to expand...
Ye the 32bit version is really stable, I just find that really weird :p
 
Tarek1337 said:
Haha i agree. :p, But as i asked. Is x64 stable for the official TFS datapack?
Click to expand...
I have only had problems with the 64bit version on ORTS so yes.
 
One odd thing I did notice when running the 64bit version with ORTS is that RAM usage caps at 2.8Gb and won't go up anymore.
 
Really? That's maybe the problem. Because our x86 server with orts take 4.6 GB ram. o.o Report this issue on github.
 
Well, i have the crashlog on the MVS. But i have no idea how to read it, i'm used to linux.

@Mark
TWTi9Q3yA.png
 
Thats pretty much the exact crash log I get from the MVS debugger too. The oddest part about the x64 bit server maxing at 2.8gb is that's usually the 3GB barrier, does that mean it could be somehow limited to only using 32bit memory addressing? I've seen this happen with some other games that run both 32 and 64 bit clients.
 
CrazyTolradi said:
Thats pretty much the exact crash log I get from the MVS debugger too. The oddest part about the x64 bit server maxing at 2.8gb is that's usually the 3GB barrier, does that mean it could be somehow limited to only using 32bit memory addressing? I've seen this happen with some other games that run both 32 and 64 bit clients.
Click to expand...

Could you try to add <LargeAddressAware>true</LargeAddressAware> in <Link> in vc12/arch64.props, recompile 64-bit and see if it makes any difference?
 
Mark said:
Could you try to add <LargeAddressAware>true</LargeAddressAware> in <Link> in vc12/arch64.props, recompile 64-bit and see if it makes any difference?
Click to expand...
Just tried it now, started at 2.831GB of RAM and slowly kept growing in RAM use at about a rate of 1mb of a minute. Hit 2.844GB and crashed, same debugging info as before.
 
still amazed that @Mark is still pushing out this software, free of charge, for so many years. Big kudo's, deff a key person in keeping ot community alive.
 
CrazyTolradi said:
Just tried it now, started at 2.831GB of RAM and slowly kept growing in RAM use at about a rate of 1mb of a minute. Hit 2.844GB and crashed, same debugging info as before.
Click to expand...

I've updated the release with a hotfix and at the same time also updated LuaJIT from 2.0.2 to 2.0.4, which may or may not make a difference. Could you try redownloading and let me know if there's any difference?
 
What database should I use?

Nevermind, I've forgot the schema.sql. I'll try to run a 10.77 Azeroth for my friends :3
Thanks and great work :3
 
Last edited by a moderator:
what do you think, it is possible to move server from 0.3.6 to 1.1?
 
Status
Not open for further replies.
Back
Top