Wesnoth 1.18.2

[Pentarctagon]

Wesnoth 1.18.2 is out!

Get on itch.io

Get on Steam

1.18 Release Notes

This is a regular maintenance release for the stable 1.18.x series, delivering bug fixes and translation updates. As is the norm for updates to the current stable series, this release is fully compatible with previous 1.18.x versions.

A full list of changes and new features added since version 1.16 can be found in the release notes for this series.


Downloads

Steam
The latest stable version of Wesnoth is published on Steam and regularly receives translation updates between releases.

Itch.io
The latest stable version of Wesnoth is also published on itch.io. A standalone portable download is also available.

Windows installer
SHA256 sum: 3a83338eb85c9b9d6e7985c1c0bb9fdf59594fe04c72e261c4290ce9f586e0f6
NOTE: Due to how expensive it is, Wesnoth's installer is not signed. This often results in the installer being flagged as potentially dangerous by antivirus software because the publisher is unknown.

macOS package
SHA256 sum: d53dc8ab64a59e69736bc4e1087e0fc69df5187be9bb3b9c01a86f58a81221af

Source code
SHA256 sum: 5f9f6d6105d48cf614eb06cf72273d62931dcb5d4982d75e851c3fa2fa70553a

Linux
All known Linux packagers have been contacted, and binaries for your distribution may have already been created. Information about where to get the respective binaries and how to install them, including via Flatpak, can be found on the Linux binaries page in the wiki.

Changes in this release

Read on for more details about the most notable fixes and additions since the previous stable release. A full list of changes may be found in our changelog.

[ Expand all ]

General

Fixes»

• Something is wrong with the addon version check database
  The error "Something is wrong with the addon version check database supporting the multiplayer lobby" in situations where there was nothing wrong has been fixed.
• Undo/redo out of sync errors
  Fixed cases where bad handling of undo/redo could cause out of sync errors.

⁂

If you find any bugs, do not hesitate to report them, but please read the instructions on how to report bugs first! As bug reports in the forums tend to be forgotten, you will get better results using our bug tracker. We require your help for finding and fixing issues, no matter how obvious, trivial, or complicated they seem!

Have fun!

[gnombat]

Before I try to narrow this down any further: has anyone noticed version 1.18.2 leaking (a lot of) memory?

Today I noticed it was using over 14 gigabytes (and still growing):

[Ravana]

[advancement][filter]formula has memory leak. Not sure if that is your use case too.

[ERROR1025]

1.18.0~1.18.2 have HIGH GPU 3D use,how fix?
I use NVIDIA GTX GPU,play 1.16.* in office 1V1 map only use <5% GPU 3D,but 1.18 have >50% GPU 3D.
I thy remove add-on ,but can not fix.

[Soliton]

Before I try to narrow this down any further: has anyone noticed version 1.18.2 leaking (a lot of) memory?

Today I noticed it was using over 14 gigabytes (and still growing):

Note that virtual size usually means quite little. It's just reserved address space that may or may not be actually used. Physical memory is typically what is actually used (and it gets more complicated since processes share memory etc). On MacOS for me wesnoth uses virtual memory of ~390GB right after start for example.

That is not to say that there are no memory leaks of course. Ravana mentioned one issue and there are likely more. When keeping wesnoth running for a while (maybe in the lobby? been a while since I tried to figure it out) on MacOS at least physical memory use does rise more and more. Unfortunately it's not so easy to find out what the cause is...

[gnombat]

Note that virtual size usually means quite little. It's just reserved address space that may or may not be actually used. Physical memory is typically what is actually used (and it gets more complicated since processes share memory etc).

When the above screenshot was taken, physical memory was probably not a very useful metric because most of the Wesnoth process was likely swapped out to disk at that point. (I should mention that, at that time, the system was noticeably swapping and becoming increasingly unusable.)

"Private Bytes" might be a better metric than virtual size, although I'm not sure exactly what it is measuring.

On MacOS for me wesnoth uses virtual memory of ~390GB right after start for example.

On Windows it does not do that (or at least, not to that extent). On Windows the virtual size is usually around 4 GB just after starting Wesnoth, and it usually does not change very much when playing a campaign.

The above screenshot was taken after playing a few scenarios of Venomous Sands, during which the virtual size seemed to be growing by up to 100 MB per turn. After a few scenarios (roughly 100 turns) the virtual size had grown by about 10 GB.

I have played some other campaigns on 1.18 and have not noticed any memory leaks. But other people have observed leaks in other campaigns (Legend of the Invincibles and A Vision Blinded), so the issue might not be unique to Venomous Sands.

[Soliton]

Ok, if the value in your screenshot is unusual compared to your "normal" experience playing wesnoth then that makes sense. Just wanted to point out that without that context such a value does not have to mean that there is something wrong.

[gnombat]

Ok, if the value in your screenshot is unusual compared to your "normal" experience playing wesnoth then that makes sense. Just wanted to point out that without that context such a value does not have to mean that there is something wrong.

It's not so much that the specific value necessarily means something but rather that the value keeps increasing over time, and memory never appears to get freed.

Here's a chart that better illustrates what's going on. This shows memory used by the wesnoth.exe process while playing the first 2 scenarios of Venomous Sands. This is private bytes rather than virtual size.

private-bytes.png (5.95 KiB) Viewed 11536 times

Here's another chart showing memory used by the entire operating system rather than just the wesnoth.exe process alone. It increases from about 7 GB to about 12 GB while playing the 2 scenarios.

system-commit.png (6.45 KiB) Viewed 11536 times

[Yomar]

Yes true, I even got an out of memory message after leabing wesnoth running for a long amount of time.

[Ravana]

Before I try to narrow this down any further: has anyone noticed version 1.18.2 leaking (a lot of) memory?

Today I noticed it was using over 14 gigabytes (and still growing):

memory-leak.png

1.19.10 fixed some memory leaks https://github.com/wesnoth/wesnoth/pull/10038