Hi,We've been on it for awhile and it does not effect a majority of users. In fact I can't even reproduce it on my measly 1 GB machine! However, we do know it is an issue are are working on getting it resolved.Thanks,

Hi Jim-I think the key here is that you have to do an extended flight, say 1+ hours. If you have AG set to normal, flying in windowed mode with task manager open, you should see memory start to creep up over time.I suspect many users aren't exceeding the 1+ hours and as a result, no oom.Mark

Hi Jim-I think the key here is that you have to do an extended flight, say 1+ hours. If you have AG set to normal, flying in windowed mode with task manager open, you should see memory start to creep up over time.I suspect many users aren't exceeding the 1+ hours and as a result, no oom.Mark

I can confirm that. I'm a FS-fan ever since BAO (remember?) and since FS made it possible to fly transcontinental, I almost always fly trans-Atlantic flights from EHAM with the PMDG 747-X (FSX, Vox-ATC, FS-PassengersX, WindowsXP, 3GB switch, 4GB RAM, 8800GTS 640MB). Since using ASA, I've flown at least 10 of those flights, but never reached my destination (KJFK, KORD or KATL). I can manage to cross the North Atlantic, but on reaching Newfoundland or Canada (I always use the daily NAT's in FSBuild), I get the dreaded OOM-error. One other thing I noticed: when starting ASA and then FSX, the ASA weather is not loaded right-away. When I load the PMDG 747X airplane the ASA weather is loaded also! Very strange! Furthermore: above sea ASA is able to tame the cradling effect of the PMDG 747 completely (altimeter is rock-steady). However when above terrain, the altimeter starts cradling again (though not as much as with ASX or FS-weather).Jan

Hi,We've been on it for awhile and it does not effect a majority of users. In fact I can't even reproduce it on my measly 1 GB machine! However, we do know it is an issue are are working on getting it resolved.Thanks,

Mr. support manager, please try doing a 1+ hour flight with ASA in some of the high density airports of FSX like KLAX or something like that with all settings set to HIGH in FSX with a 1GB machine and please report back. I'm very sure a 1GB machine will die on the spot and a 4GB machine will die (OOM) as you approach KLAX. Most of the OOM only occurs when u start panning around views a lot. Another IMPORTANT!!!! point to note. All we simmers like to watch replays as soon as we take off or land. Most of the OOM's occur when we switch back to real flight after watching replays. this is another thing that has to be kept in mind.regards, Ashwath.

This OOM problem...seems very odd it was not caught in the beta process concerning the FSX beta testers anyway. I can think most Flight Simmers who choose to purchase ASA or any of the fine products that proceeded ASA are more geared toward being a " Hardcore " simmer, meaning more then just a game player but one who wants to add reality and get " as real as it gets " with the hobby. With this in mind many buy more complex products concerning aircrafts,sceneries and environment programs and even recording programs to capture all the glory of the hobby...oh yeah and ACARS programs which are used for Vitrual Airlines that need to be running along with every else...phew weee, it all takes it

Try this, if you haven't already -- it seems to have worked for me -- http://support.microsoft.com/kb/892610I had been wrestling with OOM issues as well as FS9 CTD'ing at the very end of a flight session since I bought the Wilco E-jets in late September. I had been particularly perplexed with a CTD trying to save a situation at the end of a flight with any of the planes from the Ejet series with a default plane before exiting.Recently, I also uninstalled and reinstalled Ultimate Traffic which I've used for years after finding that there were a number of planes without textures for some reason, probably user-related and causing a memory leak. Since following the instructions from the MS technote above, I have done two 90 minute flights with ASA (via Wideclient which can be more forgiving) with 8 cloud layers, through severely overcast conditions, with Megascenery SoCal to Mega Norcal, Fly Tampa San Diego to Fly Tampa San Francisco, with the Wilco E-jet 170 with NO OOM or CTD. In fact, for the first time, I can now swap out the ejet for a default plane before saving my situation and NOT experience the CTD behavior I had been religiously experiencing up to this point.This may all play differently with all programs running on the same pc but in this particular case with a Wideclient handling the load of the ASA interface, rebuilding the page file of my Windows XP 32 bit machine seems to have resolved the issue. Note that I also performed the steps in the technote before each flight.Perhaps this might help some with this issue. It would be curious to know results.Ed Lin, D.O.S.

Hi,just adding this post to supply some more information for the Hifi-team. I

I have also suffered from an oom while using ASA. I am trying to stop a fsuipc error at the same time, so im not having a great deal of luck with this product... :(

Well, count me in as well... Core2Quad Q95504Gb Corsair ValueSelectVista x86FSX SP1 + SP2ASGASA with ASG snapshotsMy first online flight with FSX tonight KDEN - KSFO (wilco 737 PIC)... Weatherscape was awesome! Had heavy snow at KDEN.... About 45 minutes into the flight FSX froze and SB4 lost connection with FSX. Upon closing FSX I had the infamous "You computer has run out of available memory..." sitting on the desktop.Hope this gets worked out soon...Robert

Try this, if you haven't already -- it seems to have worked for me -- http://support.microsoft.com/kb/892610I had been wrestling with OOM issues as well as FS9 CTD'ing at the very end of a flight session since I bought the Wilco E-jets in late September. I had been particularly perplexed with a CTD trying to save a situation at the end of a flight with any of the planes from the Ejet series with a default plane before exiting.Recently, I also uninstalled and reinstalled Ultimate Traffic which I've used for years after finding that there were a number of planes without textures for some reason, probably user-related and causing a memory leak. Since following the instructions from the MS technote above, I have done two 90 minute flights with ASA (via Wideclient which can be more forgiving) with 8 cloud layers, through severely overcast conditions, with Megascenery SoCal to Mega Norcal, Fly Tampa San Diego to Fly Tampa San Francisco, with the Wilco E-jet 170 with NO OOM or CTD. In fact, for the first time, I can now swap out the ejet for a default plane before saving my situation and NOT experience the CTD behavior I had been religiously experiencing up to this point.This may all play differently with all programs running on the same pc but in this particular case with a Wideclient handling the load of the ASA interface, rebuilding the page file of my Windows XP 32 bit machine seems to have resolved the issue. Note that I also performed the steps in the technote before each flight.Perhaps this might help some with this issue. It would be curious to know results.Ed Lin, D.O.S.

I did this easy procedure and I must admit, it has worked for me...thanks so much for the time in posting this. :(

hi allthink this happened to me today on vista 64bit :(

DescriptionStopped workingProblem signatureProblem Event Name:	CLR20r3Problem Signature 01:	asa_exec.exeProblem Signature 02:	11.0.0.316Problem Signature 03:	494fcea1Problem Signature 04:	ASAProblem Signature 05:	11.0.0.316Problem Signature 06:	494fce9fProblem Signature 07:	4bProblem Signature 08:	0Problem Signature 09:	System.OverflowExceptionOS Version:	6.0.6001.2.1.0.768.2Locale ID:	2057Extra information about the problemBucket ID:	418928853

happened in a dc3 21.00 gmt today on a flight between FKYS >FKDD had a lot of turbulence and some lightning visible (in case it matters) xgraphics texture snapshots used.Im not sure how to get to the ASA logs to give you those..only thing ive changed is I recently purchased and installed FSpassengersX.. Mike...

Same problem here. Typically on longer flights I get the OOM error. Never had that problem with ASX.

Add me to the list, OOM within an hour or two. /3GB switch installed an 4GB physical ram. Had problem with last release of ASX and now with ASA . . running beta patch 355 . . .Can't wait to hear if a soluction is in the works.Joe

You can add me to the list has well.

Hi,Are you running B355?Thanks,

Am I missing something???? I propose this:If Users A, B, C run ASX and ASA for hours and hours with no problems.And User D, E run ASX or ASA and have problems...It doesn't make sense to me that ASX or ASA is the problem. Code is Code and it runs the program as it is compiled... this doesn't change based on Computer A, B , C, D, or E.I would think that maybe ASX or ASA is stressing the system in a way that former faulty code that did not show an issue is now rearing it's ugly head and to the casual observerit appears that ASX or ASA is the issue when in fact it is most likely something else.Don't get me wrong I am sure there are issues with ASX or ASA that are stressing FSX and or the computer system and are causing issues, these issues will be present on any similary configured computers.Working with add-on software is like creating a widget to put on your car to enhance a basic function of your car. The widget may be perfect, and the car it is in the real problem.I'm just amazed with some of the comments I read!!!

I als have OOM`s in FSX only when I use ASA. Vista32, 4GB memory and 3GB-switch installed.I hope, there will be a solution.....Best wishesLars