by peterhayes » Thu Oct 10, 2019 4:30 pm
This is an error that is unrelated to the amount of RAM installed, memory leaks, etc. What has happened is that a badly scripted software app eg WS Scenario/Route has tried to write to an address in the RAM that is protected, unavailable or simply does not exist. This can also happen in the editor in 64-bit mode. Using another example, now that TS2020 64-bit can access up to 8 TERABytes of VAS, the current coding may be unable to find, in some instances, the memory address needed by the working set. This creates an Invalid Page Fault and TS terminates with a 0xC0000005 error. Possibly incorrectly displayed as "out of Memory" by DTG in TS, but perhaps that's the only option Windows allows.
In TS 2019 and/or TS 2010 once the OS/VAS has loaded a scenario into the working set of the RAM (approx 4.5Gb on average) this does not vary by much more than 5/6% in addresses accessed, even in the longest scenarios. I have left TS2020 running a scenario overnight on pause, and RAM allocation was constant with very little variation. Even an 8 hour JT Western Mainlines scenario saw only minor variations in the % RAM addressed. Monitored dynamically with Pulseway app on an iPad.
Unfortunately, this is an idiosyncratic error peculiar to an individual PC - there are between 80,000 to 800,000 registered TS2020 users (I'm not sure which figure is correct) but can you imagine the number of posts on websites such as this, if it were a universal error?
I have never seen an "Access Violation", OOM, error when running DTG, RSC, JT, AP, DPS, TaD, UKTS, etc, etc DLC, but have many times when automatically loading a WS scenario, go figure.
pH