RomRaider

additionally, it may be nothing. It seems high, but it doesn't mean the application is actually using that much memory, just how much is allocated by Windows (and this may change if other applications need it). Vista may do something different with memory allocation.

How much total ram is installed on the system? Also try minimizing Learning View as see how it changes.

Yeah I agree that vista does a lot of caching... When i minimize it, it goes down by like 1-2mb.
The thing that bothers me, is that when i start up the app, it only uses like 30mb. When i click connect, i see the actual used memory ramp up to 1gb rapidly, then drop back down to 100mb. Its this 1gb ceiling that seems way off.

I'm not sure why it was up over 300mb actual ram before, but i had it running for about 4 days, and had updated the data a few times per day.

Still seems to me that something isn't right memory usage wise. For example Microsoft Outlook 2007 on my box of only 170MB.

This laptop has 4gb of ram.

Thanks for looking into this.

The problem is that it is not the actual total amount of memory being used by the application - only allocated. It may allocate much, much more than is actually needed and this could vary by the amount of free ram and the number of other applications running. Then when other applications need the memory, it will be reallocated. Try opening a bunch of other memory hungry applications at once and see what happens.

The fact that it is only 1-2 mb when minimized means this is likely the case and there's probably not much I can do about it, but I will look into it.

The spike seen when connecting is due to the definitions which are temporary loaded after the ecu id is determined.

No, when the app is minimized the memory usage goes "down a few megs", meaning that it is still over 100mb. I understand how caching works, and how aggressively vista does it, but I don't see why the memory usage should ever hit 1gb. When I clicked connect, I watched the actual "Private bytes" count up from around 30mb to over 1gb, then drop off to around 100mb. It seems that a TON of data is being loaded up into memory at once, and maybe this can be cut down to do it in chunks... Load up some, check, free it, load up some more, etc...

I'm not complaining, this app is amazing and very valuable for everyone in this forum. I am just reporting what i see.

I'm a .NET dev, so i'd be happy to take a look at what the issue might be, if you'd like. But it sounds like you are keeping it closed source, so thats probably not a possibility.

To diagnose, you could try adding a button that calls GC.Collect(). If memory consumption goes way down, then there's nothing to worry about, the high usage just means the garbage collector hasn't yet felt any need to collect. If it doesn't go down, then it's time to look for the cause.

I'm told that .Net's XML DOM is pretty memory hungry. See if you've got something that's still referencing the XML DOM for the logger definitions, after it's no longer needed. In other words, see if you can copy the values you need for the current ECU, and then let go of the XML document.

Or look for a collection that grows indefinitely. Or look for code that adds event handlers and make sure it either only runs once, or there's corresponding code to remove old event handlers. That bit me once.

I'll try the release version tomorrow on my own car (rather than a virtual ecu) and report back.

Tried the official release by actually connecting to the ECU. 17mb before connecting, 20mb after, remains at 20mb after multiple re-connects. Peak is 47mb very briefy which coincides with the temporary loading of the defs after ecu id is determined (defs are only about 30kb). So, everything looks fine. This is laptop running XP and 2GB ram.

I think the issue is normal relating to Vista and a lot of free ram. I don't claim to be an expert in memory management, but it appears Vista is allocating an ass-load of memory to Learning View because you have an ass-load of free ram. Try running a bunch of memory hungry apps at the same time and see what happens.

i have a questions for you guys

what am i supposed to do with the airflow ranges should i adjust anything for it or what?

You nailed it. I am rescaling maf and it is off in this range by a good bit. Nice one Mickey.

Here is mine: Any comment?

The AFR Learning A might indicate a small leak near or before your front O2 sensor. I would take off the plastic shield and look for soot marks on the exhaust manifold joints.

hmm...maybe I do have leak somewhere. I can hear weird pulse noise(like steam train) at low rpm when car is moving.

Have to take a look at it this weekend.

Any ideas on my fuel learning B area? Seems a little high to me.
Any ideas on why it is so high there?

I wouldn't worry about AFR Learning B. It could be an anomaly. My AFR learning B takes forever to stabilize because I almost never drive constant there. It seems like the ecu only updates AFR Learning if the driving condition is near steady state. Even if you did have a real dip in your MAF in that range, it wouldn't really affect your driving very much. The only way to be certain is to do a slow drive with constant throttle in that range and log trims and make the adjustment after making sure you have enough data.

There is a giant empty parking lot here that I use for that.

I would be more concerned about the IAM < 1.

BTW, I forgot to ask: should I worry about this? Does that mean I'm running too lean and ECU has to add lots of fuel?

Thanks.