I've been struggling with a similar issue for the last few weeks and was about to submit a support request (which I might still do). I too have not had any issues for a long time, especially since switching to FSX-SE which immediately solved the last of any VAS issues. However upon the release of the new KSFOHD, I planned YSSY-KSFO noting that I hadn't done that sector since parking the 747-400X (using the older Flightbeam KSFO) but had done YSSY-KLAX a number of times in the 777. Left the flight going overnight only to find an out of memory error message near the equator. I conducted a number of repeats, recording VAS as I went and noticed how it was being eaten up as time went on. I conducted 4-5 flights, changing different settings each time, and for each of them, after 6-7 hours, it was obvious I wasn't going to make it across the Pacific.
So I bit the bullet and rolled over to Windows 10 and did a fresh install of FSX-SE, then the 777 and nothing else. Flew YSSY-KSFO and watched 1.8GB of VAS dissolve away. No traffic. No weather. 1024 for the textures. etc.
Noting my flight took me over Fiji, I loaded FlyTampa YSSY and flew YSSY-NFFN in the NGX no problems. Tried the 777 and all OK too. No loss of VAS. Stayed around 1.5GB remaining all the time once clear of YSSY.
Tried a different route for YSSY-KSFO. VAS slowly dissolved again.
Last night I tried YSSY-KLAX and VAS held constant at 1.2-1.3GB remaining the whole flight and only dropped getting close to the airport (as expected for the Dreamteam KLAX).
So there is something going on for KSFO, whether default or not. I did pre-load the approach on all occasions, so perhaps I'll try not entering the approach until later in the flight, which is more realistic anyway.
But I am in some ways happy to see that I'm not the only one having issues........
Darryl Taylor