Windows 10 Memory Leak Fixed
We're not sure when this problem was introduced, but we started seeing reports of it after the deployment of Ascendancy.
We initially dismissed reports of a memory leak because:
We were wrong and would like to publicly apologise that this went on for so long. There was a leak and after many days of investigation, we have fixed it. Strangely, it appeared to be a regression in Windows 10 that caused previously normal behaviour to now leak System memory. To take advantage of this update, just restart your game client once and the hotfixed version will download. Thanks very much to the users who contributed RAMMap reports and other information that helped us diagnose the issue. We are still working on improving other memory issues as well. We have some promising memory reductions that will hopefully be deployed in the coming week. These should resolve the memory-related crashes that people sometimes encounter when changing areas. I'd like to deeply apologise for the recent performance issues, and thank you for your patience. We have several programmers dedicated to performance improvements and they have a lot of plans for how to continue to improve our architecture. Last edited by Chris on Mar 22, 2016, 12:40:20 AM Last bumped on Dec 23, 2019, 9:17:02 AM
| |
" If it was the memory problem then that'd crash with a windows (possibly saying MapViewOfFile). What's the error shown here when you're disconnected? | |
" For some users, yes. |