Setup runs until "Out Of Memory" error occurs

[spicymikey]

Hi,

This is going to be a tough one. In fact, I've been having this issue for months but didn't bother posting it since I had so little to share to start a troubleshooting session. But I'm out of ideas and it's happening more and more often now, so here goes!

We have about 3000 installed PC's using this setup. About 10% of these installations exhibit an "out of Memory" error when running the setup. Here's what I know
- It is not specific to any particular OS. Happens on all our supported platforms; Vista, 7, 8, and 8.1
- It only seems to happen on subsequent setups with the product already installed
- Setup starts fine and throws up the splash screen, but then it just churns.
- Task Manager shows the setup.exe growing rapidly in "Memory" until it reaches a point that causes Windows to flush it with an "Out of Memory" GPF
- Removing the product and then manually locating and removing ALL prior cached copies of setup.exe and all temp files related to mia, etc., solves the problem

I have looked for a cause on and off for months but have no idea what it is. Has anyone else experienced this? Could it be something in the script causing this? if so, I can't imagine why it doesn't always happen to all installs.

[FrancescoT]

Dear Mike,

which InstallAware version are you using?

Regards

[spicymikey]

Sorry Francesco. For some reason I was not alerted that there was a response. I was just coming here to add more info and saw your posted question. This is IA X2 Build 4.03.15 (according to the splash screen)

But I have some more info as a clue. The error message says the "Out Of Memory" is occuring on line 247. That line is:
"Load Feature Selection from file $APPCOMMONFILES$\SetupConfig.dat"

I looked at the SetupConfig.Dat file on that computer and the files is a whopping 441mb!! I guess that makes sense that it is struggling to load it. Bigger question is why is it so big? I cracked it open and looked at it. Seems normal and has text data saving the setup config. Problem is that it seems to just repeat itself over and over and over. This file is saved in my Finish routine simply by executing the following command:
"Save Feature Selections Into file $APPCOMMONFILES$\SetupConfig.dat"

I tried an install on a fresh computer. The file looked good. Yet, for every subsequent install, the file kept growing and doubling in size everytime. I can see how over time the file will grow exponentially and become huge. The strange thing is that this file is deleted after every install. So I don't know what mechanism is causing this to "remember" there was a prior setup and to keep doubling. I tried setting LOADOLDDATA = FALSE and that didn't help either.

I have no idea how to troubleshoot this because the loading and saving of config settings seems mostly handled by IA and is just magic for us. Any ideas what to look for would be appreciated.

[FrancescoT]

Dear Mike,

first of all you can check the IA version from Add Remove Program (control Panel). The one reported by the IDE is the build number.

For what concerns the error you reported, it seems that I am able to replicate the same.
I'll let you know, I need to investigate on it.

Regards

[spicymikey]

Glad you see the issue on your end also.

Per the Control Panel, the version running here is 19.08.0.2015

[FrancescoT]

You are using the latest update!

Regards

[spicymikey]

Any solution on this Francesco. The problem is that this must have been happening since we upgraded to the latest version and we didn't notice it. Now it's been long enough that these files are reaching a size where they are causing the out of memory issues. Each day now more and more customers are reporting it. Right now we are telling them to delete this file but there is "memory" of the installation somewhere and the next time they install it the size is back to the prior size, plus doubled again.

[FrancescoT]

Dear Mike,

I have informed our dev team about the problem.
Unfortunately, I haven't received any news yet or information about possible workaround to use.

I'll be back to you as soon as I receive any info.

Regards

[spicymikey]

OK thanks for the update. You're usually so good at finding an answer and workaround quickly! I guess this is a bigger one than normal. Leave it to me to find this stuff. :/ I may consider just disabling the feature for now if you don't get an answer soon.

What is that LOADOLDDATA variable? Can that help us in any way?

Mike

[FrancescoT]

Dear Mike,

the LOADOLDDATA pre-defined compiler variable replicates almost the functionality that you have using "Load Feature Selections" command ... but honestly, I am not quite sure if using it, you can skip the problem.

Regards

[spicymikey]

Hi Francesco,

Any status on this issue? I've tried a few other things to see if I could make it stop happening, but I cannot. Loading and saving Feature selections seems like an important feature that a lot would use. Hope there will be a fix soon. If not, can you suggest any workarounds? Our installer has a lot of optional features and we like to capture the configuration from the last setup to make it easier for the customer to reinstall the software when new versions are released.

Thanks

[FrancescoT]

Dear Mike,

currently the only possible option it's use a custom script code to store in a file all the information required.

Regards

[spicymikey]

Thanks Francesco. What about the first part of the question? Any status on the problem and when it will be fixed?

Mike

[FrancescoT]

Dear Mike,

unfortunately I haven't received any info from dev team.

Regards

[spicymikey]

Hi Francesco,

That's not good. You and I deserve more. I'd appreciate you pressing them and reminding them this is an advertised feature in their latest version with no workaround. Tell them I understand there are priorities, but I deserve an ETA on a fix. I think it's a reasonable request because if I know the fix is imminent I will wait for it. If they have no plans to fix it then I'll have to make other arrangements.

Thanks
Mike