Memory Leak over Canada ?

[Speedbird 217 127]

Hi,

I just did a LHR-SAN and SAN-LHR over the weekend.
Enjoying P3Dv3's new VAS management I had between 1.1 to 1.2 GB free after take off on either flight in the PMDG 777 on Rob's recommended settings.

After take-off from LHR I had 1.2 GB free until reaching Canada, at which point it suddenly dropped to 800 MB and further decreased down to 500 MB at its minimum.
I could still land in SAN without OOM and about 400 MB remaining thanks to the improved VAS management, but it seems very strange that Canada just "swallowed" 700 MB of VAS that would not be released back.

Today I did the return flight and again, just as I approached the Canadian border VAS dropped from 1.1 GB free to 800 MB, decreasing to a minimum of 400 MB left while over Canada. As I flew out over the Atlantic it increased back to 700 MB remaining and I could land in LHR with 400 MB remaining.

Does anybody have any idea what is causing this? It's not exactly a demanding region, there's not much there in Northern Canada that would result in such a VAS drop, especially considering that in LHR I have 1.2 GB free. It almost seems like there is a memory leak in the region somewhere, my current main suspect is OpenLC Canada. Please see below for the flight path on the way back with the "VAS Black Hole" highlighted in red.


 
Addons used:

-AS EGLL
-LVFR KSAN
-PMDG 777-300ER
-ASN Live Weather
-REX Texture Direct + Soft Clouds
-Pro-ATC X
-FTX Global
-FSGlobal 2010
-OpenLC Europe
-OpenLC Canada & Alaska (I somehow suspect this to be the culprit, even though I don't experience any issues with OpenLC Europe)
-FTX Vector with only highways and main roads turned on - not causing any issues in Europe or USA

[JRBarrett 3,073]

It certainly does look like OpenLC Canada/Alaska would be a strong suspect. I recently installed the new Orbx OpenLC North America in P3D V3, but have not as yet made any flights north of the US border. When I do, I'll check for this problem...

[Speedbird 217 127]

Just to provide an update; I flew LHR-AUS today and the same thing happened over Canada - VAS going from 1.1 GB to 400 MB. This time I had OpenLC Canada turned off, so that doesn't seem to be the cause. Thanks to P3D I could still land without an issue as it released VAS as I was approaching the airport, however Canada still uses 700 MB of VAS.

 

The only other addon that is active and affects Canada would be Vector. As said before, I only use highways and main roads and not many other features plus the fact it's working fine in other regions.

No idea what is causing this, it seems to be some sort of memory leak in the area.

[Guest]

I have all of those add-ons installed except Orbx FTX Vector.  I have not experienced any VAS issues like that in V3 over that part of the world Canada.  But I have seen the memory consumption issue you mention (very rapid consumption of VAS) going back to V2.5 ... I have not seen it since in V3.  There were certain areas (back in V2.5 days) that would cause rapid VAS consumption ... FL heading out to Atlantic ocean (exactly as I cross over coastline), Antartica (Aerosoft) just flying over a remote region with no real "density" of anything, Copenhagen (this turned out to be single BGL issue with FT or some conflict), KLAX heading out to Pacific ocean (nothing in sight, again crossing over a coastline).  Could it be "coastlines"?  Could it be a region boundary?  I don't really know.

 

As much as I like Orbx FTX Vector, I'm holding off on installing it again ... I have ran multiple tests with clean installs (Orbx only) and wasn't able to replicate the VAS issue.  But when I start adding other 3rd party content into the mix, that's when I had these rapid VAS consumption issues.

 

Sadly I have no answer as to what caused the rapid VAS consumption, I have only theories with no solid foundation.  One of those theories is that somewhere along the line a GUID reference in Terrain.cfg got subverted and is referenced thinking it's XYZ when it's really something else (that item consumes considerably more VAS).  I did work with LM extensively on the problem I could replicate (again back in v2.x days), but they weren't able to duplicate -- it's highly likely some very obscure issue that takes a very specific set of changes to induce the problem.

 

Every time I thought is was "product XYZ", I would wipe and re-install V2.x, install 3rd party add-ons except that I suspected caused issue, VAS was good - no issue ... then I install suspected 3rd party add-on (expecting to see the issue) but still no issue.  It was frustrating because I could clearly see it happening on my main PC but not on my test PC.  At that point I could see I was getting no where so asked LM for any type of diagnostic tools I could use to help me resolve ... they didn't have any other than their own VS debug environment.

 

The two files you might want to check are:

 

Default.xml  (in ...\Lockheed Martin\Prepar3D V3\Autogen - for example FT airports can change these files)

Terrain.cfg (in ... \ProgramData\Lockheed Martin)

 

But like I said, so far in V3, I've not had a single issue with VAS.

 

Cheers, Rob.

 

EDIT: This may sound strange relative to your issue, but what CPU are you using and do you have HT enabled?  I do believe there is some issue around having too many CPUs because I can't understand why HT OFF on my 5960X reduces my VAS usage by 400-500MB ... only explanation I have is that duplicate threads are running the same task and hence the higher VAS usage.

[Speedbird 217 127]

Thanks for your detailed response Rob.

 

I'm using an i7 4790k with HT off on 4 physical cores without any AM setting.

 

Any ideas what to look for in the two files you mention? I did a quick check and the only custom entries I could find were from ORBX products and libraries.

[GAMERZSOCIAL 0]

Hello

 

I'm experiencing the exact same issue. There seems to be some form of memory leak over the same part of Canada that you have marked on the globe. I'm also using the same addons as you.

 

I do have a 5960X with HT enabled, but I see no real reason to disable this, considering the CPU is used for other things that require HT.

 

I did a flight last week from LHR to LAX and I noticed the memory peak. I had about 8% VAS remaining. As I got closer to LAX, the VAS reduced back down to, leaving me with 12% remaining. It went back up to having 10% remaining on landing, which was fine.

 

On the flight I did last night, from SFO to LHR, the memory leak appeared again, but this time the VAS did not reduce, resulting in an OOM just before turning onto final. 

 

Any luck with finding a way around this? Hopefully it is fixed, because this is annoying. Only thing I can think to do is restart the sim at TOD, so I have a fresh amount of VAS for landing.

[chad556 1]

Sorry to revive an old topic, but I too am having this issue. In fact, with Open Lc disabled and only highways enabled on vector (making it almost pointless to run) I still suffer a MAJOR VAS hit in the region noted above. Loading up at the default CYYZ or CYOW in the default piper cub starts with a VAS of nearly 3.1gb! 

 

[SierraDelta 1,342]

Let's get the terminology correct - what we're seeing is NOT a memory leak, it is simply FTX Vector springing into action. At the moment I'm approaching the Canadian / US border near Sault Ste Marie on a flight from LHR to IAH in the PMDG 777, and the NATs are so northerly today that I crossed the Canadian coast some 400 kms north of Goose Bay. Take a look at Google Maps - I have passed hundreds of thousands of lakes of all sizes and of course VAS usage increases because of that! I've been as low as about ~ 450kb left, but because of the amazing way that P3D reclaims VAS I'm now back at 750kb available.

 

It's all about managing expectations and settings. In FSX I would probably have saved and reloaded the flight when getting that low on VAS, but with P3D I'm confident that I'll recover.

[Guest]

I installed Orbx Vector but keep it limited to these settings: http://www.robainscough.com/Orbx_Vector.html

 

 

 

I do have a 5960X with HT enabled, but I see no real reason to disable this, considering the CPU is used for other things that require HT.

 

Then you will need to use an affinity mask to reduce the number of CPU's threading as 16T will consume about 400MB more VAS than 8C.  Affinity Mask calc here: http://www.gatwick-fsg.org.uk/affinitymask.aspx?SubMenuItem=hardware

 

Try 

[JOBSCHEDULER]
AffinityMask=340

 

Cheers, Rob.

[dom8984 0]

I too have noticed an issue with VAS not releasing on a flight between EKCH-KEWR this week. Around 1400mb free on departure, a drop to about 800mb free over nothern Canada, 600mb by the US/Canada border dropping rapidly as I entered the NYC metro area (unsurprising as I have DD NYC X). This was a daytime flight.

 

On the reverse flight (at night) I left NYC with around 500mb VAS free and all worked well. Available VAS increased rapidly once I was out of the NYC area with almost 2000mb free (still had 1500mb when I landed). This flight was at night.

 

All my settings are roughly in the medium range - definitely not maxed out.  Running FT EKCH, DD NYC X, ASN, BB A330, Orbx Global, Vector (tertiary roads off) and openLC Europe/Canada and Rex textures. My hyper-threading is set to off.

 

It could be that I need to dial back the settings more but I thought this an interesting topic as generally P3Dv3 is working well for me, but I have seen on a number of occasions a surprising amount of VAS being used flying over the north of Canada. And more during the day than at night for some reason....

[CaptKornDog 284]

I've noticed the issue in Eastern Canada as well.  Not using OpenLC, but I am using Vector.  So I'll have to try and isolate that next.  In each of the graphs below, you can noticeably tell when I fly approximately over Newfoundland or Quebec in hours 4-6.

 

 

 

[CaptKornDog 284]

Reporting on my results, disabling Vector seemed to stop the massive VAS loss over eastern Canada

 

 

 

I also posted my results in the Orbx forum. And will attempt these tests again for repeatability, hopefully they can be addressed.

[Guest]

Hi Kyle,

 

When testing with Orbx Vector, what options do you have enabled?  

 

This days, I only operate Orbx Vector with "Highways" and "Primary Roads" and "Beaches" enabled, everything else unchecked.

 

Cheers, Rob.

[downscc 1,327]

I also allow wetlands in Vector along with Rob's selections without a problem yet. Parks have to be turned off or we end up with a lush green park outside El Paso lol.

[edbern007 0]

Hi,

 

I just did a LHR-SAN and SAN-LHR over the weekend.

Enjoying P3Dv3's new VAS management I had between 1.1 to 1.2 GB free after take off on either flight in the PMDG 777 on Rob's recommended settings.

 

After take-off from LHR I had 1.2 GB free until reaching Canada, at which point it suddenly dropped to 800 MB and further decreased down to 500 MB at its minimum.

I could still land in SAN without OOM and about 400 MB remaining thanks to the improved VAS management, but it seems very strange that Canada just "swallowed" 700 MB of VAS that would not be released back.

 

Today I did the return flight and again, just as I approached the Canadian border VAS dropped from 1.1 GB free to 800 MB, decreasing to a minimum of 400 MB left while over Canada. As I flew out over the Atlantic it increased back to 700 MB remaining and I could land in LHR with 400 MB remaining.

 

Does anybody have any idea what is causing this? It's not exactly a demanding region, there's not much there in Northern Canada that would result in such a VAS drop, especially considering that in LHR I have 1.2 GB free. It almost seems like there is a memory leak in the region somewhere, my current main suspect is OpenLC Canada. Please see below for the flight path on the way back with the "VAS Black Hole" highlighted in red.

 

 

Addons used:

 

-AS EGLL

-LVFR KSAN

-PMDG 777-300ER

-ASN Live Weather

-REX Texture Direct + Soft Clouds

-Pro-ATC X

-FTX Global

-FSGlobal 2010

-OpenLC Europe

-OpenLC Canada & Alaska (I somehow suspect this to be the culprit, even though I don't experience any issues with OpenLC Europe)

-FTX Vector with only highways and main roads turned on - not causing any issues in Europe or USA

 

Hi,

 

I just did a LHR-SAN and SAN-LHR over the weekend.

Enjoying P3Dv3's new VAS management I had between 1.1 to 1.2 GB free after take off on either flight in the PMDG 777 on Rob's recommended settings.

 

After take-off from LHR I had 1.2 GB free until reaching Canada, at which point it suddenly dropped to 800 MB and further decreased down to 500 MB at its minimum.

I could still land in SAN without OOM and about 400 MB remaining thanks to the improved VAS management, but it seems very strange that Canada just "swallowed" 700 MB of VAS that would not be released back.

 

Today I did the return flight and again, just as I approached the Canadian border VAS dropped from 1.1 GB free to 800 MB, decreasing to a minimum of 400 MB left while over Canada. As I flew out over the Atlantic it increased back to 700 MB remaining and I could land in LHR with 400 MB remaining.

 

Does anybody have any idea what is causing this? It's not exactly a demanding region, there's not much there in Northern Canada that would result in such a VAS drop, especially considering that in LHR I have 1.2 GB free. It almost seems like there is a memory leak in the region somewhere, my current main suspect is OpenLC Canada. Please see below for the flight path on the way back with the "VAS Black Hole" highlighted in red.

 

 

Addons used:

 

-AS EGLL

-LVFR KSAN

-PMDG 777-300ER

-ASN Live Weather

-REX Texture Direct + Soft Clouds

-Pro-ATC X

-FTX Global

-FSGlobal 2010

-OpenLC Europe

-OpenLC Canada & Alaska (I somehow suspect this to be the culprit, even though I don't experience any issues with OpenLC Europe)

-FTX Vector with only highways and main roads turned on - not causing any issues in Europe or USA

Hi there.  I know this is a late reply and you may or may not have had your issue resolved but I just recently figured it out. I am also posting this for others who may have recently encountered this problem. I had a very similar problem as you described. For me the culprit was ORBX VECTOR. Simply disabling vector in the scenery library when it comes to flying in that region was the answer for me. I always knew ORBX had a major role in OOM despite what the people at ORBX say, just that I didnt know if its all of their products causing it or just one but I always liked ORBX products and did not want to consider getting rid of ORBX altogether. At first I thought it was the ORBX LC Canada and America but when I disabled them there was very little to no difference in VAS, but the moment I disabled vector... no problems. VAS issue in the Toronto area was so bad for me sometimes I would get the OOM warning just a couple of minutes after loading it for the first time in game. Whether I use FlyTampa Toronto or not I don't have to worry about rapidly having my VAS eaten up. Vector also messes up with CYTZ scenery (at least in P3D) causing trees and buildings to be in the ocean surrounding Billy Bishop airport. Vector is a nice addon to have but it some cases it proves better to do without it.