My last two attempts up AdZ have abruptly ended after turn 8, due to memory exhaustion causing Windows to kill Zwift and everything else. This happened in February during a small meetup and again yesterday during ToW.
I haven’t had this issue in other rides or routes that take more than an hour and I have been able to complete AdZ before, so maybe there’s a regression in a recent update?
System info:
Hi
I did my usual four Alp repeats on my Win10 machine yesterday without problems and also a double alp the day before.
I get that this doesn’t help you that much, but at least it indicates that it’s not a general Win10/Alp issue.
BooX
I feel like I’ve seen more and more reports of these “memory exhaustion” issues cropping up since the recent Zwift updates.
Memory exhaustion sounds like a “resource-exhaustion-dectector” warning error that you might find in your Windows Event Viewer (e.g. EVTX) crash logs.
To my knowledge, this has to do with a low virtual memory condition and can typically be corrected by increasing the page file. Maybe check out this article and see if that helps.
Hi!
I’m having the same issue. I had three crashes this week trying to complete the long ride in stage 2 of TOW 
In my case it’s a rather old laptop on Windows 10 Home, Intel Core i3 M350 and 4GB RAM.
The event viewer shows Zwift was using 13GB at the time it got terminated.
Did you get this solved? By increasing the virtual memory? To which extend?
I did not notice the 8GB minimum requirements. This laptop with 4GB has been working fine for zwift for years until the past few days in the route to the Alpe.
If there is a memory leak, the increase in RAM sounds like a delay, not a solution. The 13GB memory used by zwift process at the time of termination would not fit in 8GB of RAM either
I upgraded the memory in my laptop to 8GB. I also increased the default virtual memory size to 20GB. As expected, that only delayed the time at which zwift will inevitably exhaust the memory because of that memory leak:
At the time of the crash it was using about 26GB of virtual memory. I don’t have the monitoring data saved, but since the upgrade the physical memory utilization is more or less stable in the range of 2GB to 4GB, which explains why with older zwift versions, prior the introduction of the memory leak, my system with the previous configuration of 4GB was running with no issues other than being old and slow.
