Difference between revisions of "Release Notes 1.15.4"
Pentarctagon (talk | contribs) |
Pentarctagon (talk | contribs) (→Instructions) |
||
| Line 1: | Line 1: | ||
== Instructions == | == Instructions == | ||
This page is for documenting changes made between the 1.15.3 and 1.15.4 releases that are especially important or otherwise notable to the end user. The description of changes added here should be more verbose and detailed than what would be included in the regular changelog on github, and most importantly, should be written with the intended audience being non-developers - no prior knowledge or knowledge of Wesnoth's inner workings should be needed in order for players to understand the entries added here. | This page is for documenting changes made between the 1.15.3 and 1.15.4 releases that are especially important or otherwise notable to the end user. The description of changes added here should be more verbose and detailed than what would be included in the regular changelog on github, and most importantly, should be written with the intended audience being non-developers - no prior knowledge or knowledge of Wesnoth's inner workings should be needed in order for players to understand the entries added here. | ||
| − | |||
| − | |||
== New Content == | == New Content == | ||
Revision as of 16:32, 17 August 2020
Contents
Instructions
This page is for documenting changes made between the 1.15.3 and 1.15.4 releases that are especially important or otherwise notable to the end user. The description of changes added here should be more verbose and detailed than what would be included in the regular changelog on github, and most importantly, should be written with the intended audience being non-developers - no prior knowledge or knowledge of Wesnoth's inner workings should be needed in order for players to understand the entries added here.
New Content
Changes To Existing Content
Fixes
Graphics engine memory leak fix
An issue dating back to version 1.13.13 was found in the game’s graphics engine that would result in large memory leaks over time, particularly evident after performing a few save-reloading or game initialization (Campaign mode, Multiplayer, Map Editor) cycles. On Windows and other systems running 32-bit builds of the game, this could eventually result in a game session crashing due to reaching platform-mandated memory limits. Furthermore, either 32-bit or 64-bit systems with small amounts of available RAM could perceive substantial performance degradation during long game sessions, or even crashes in other running software.