Many process consume ram memory

[carjona]

Hello friends ..
I am using installaware to develop an installer and later an updater for my program ... the installer generates it well, except for some things that I need to polish ... the problem is in the updater, when I run it, it downloads from the server, but later it begins to open many processes consuming almost all the ram memory of my pc.
I show you the photo

Windows Installer.png (120.98 KiB) Viewed 5264 times

as you can see many processes start
attached the project version 1

SuperStock - 1.0.rar

(1.27 MiB) Downloaded 510 times

and version 2 which is the patch that updates the first version.

SuperStockParche.rar

(1.27 MiB) Downloaded 504 times

I appreciate if you can help me.

[FrancescoT]

As first, you should verify if the same behavior can be replicated on a different machine (preferably a new clean machine - which has exclusively the OS installed).

From what I see, you are running the package from the same machine where you have IA installed.
Did you also try to run other instances of your installer in debug mode?

[carjona]

thanks for answering FrancescoT .... in my country we are in quarantine .... that's why the delay in the reply .. but still thanks

I followed your advice and made a new installation on a pc where the superstock program and the AI ​​were never installed. but it still gives the same problem:
when I open the superstock program the updater does not run directly ...
but if I go to the start menu and select the updater ... the updater window starts ...
it detects the new version hosted on my server ... download the updater ...
and then when I press start the update process so many processes are opened, that the ram memory reaches 99% ...

[FrancescoT]

Hope you are staying safe. Many of us are all in quarantine as well.
Let me see if I get any chance to find something by your project.

A question, did you modify\customize the default update process?

[carjona]

Thank you, I hope you are well too.

Regarding my project, I tell you what I want to do ... so you can clarify my ideas

We have a program that is currently in version 3.2.2.1. we never used an installer before. Until now we only created a folder on disk C and pasted all the content (an exe file and configuration files) ... usually the corrections are in the exe ... and every three months we release a new version, the next one will be the 3.2.2.2

we need to install the program for the first time, the version 3.2.2.1 (as I told you previously just paste all the files in C: \ program files \ my proyect) in each terminal of use. As the terminals are in different geographical locations, we would use the compressed web-based exe option.
we make it work properly ... I download the exe from my server ... the program installs, shortcut works ... it runs correctly ..

Now I need that when we have a modification (generally of the main exe) ... it is downloaded automatically from the web ... invisibly for the user ... and the file is replaced by the correction ...

For this we saw that the best thing would be to use the patch, since the delta between the original project and the modified project would be updated, that is, only the main exe program.

So far I think I understand well how installaware works ... now the problem is how the patch file is sent to update only the delta detected in the patch. You can see it as we put it in the .rar we upload.

but when executing the update numerous instances of the installer program are started occupying all the memory of the pc

I already read the patch pdf and web update ... and I'm still confused to find the solution. I also read other forums, such as:
https://www.installaware.com/forums/viewtopic.php?f=2&t=8619&hilit=+patch
https://www.installaware.com/forums/viewtopic.php?f=2&t=8847&hilit=+patch
https://www.installaware.com/forums/viewtopic.php?f=2&t=9343

A question, did you modify\customize the default update process?

we do not modify

[FrancescoT]

it's not totally clear to me if you had or not problems with patch.

In theory, Patches are very practical but can also have many unwanted side effects. As when an installed patch sequence become corrupted for some reasons, and this may happen when several patches have been applied on the same target installation.

Then not less important, patches are subject to precise Windows Installer rules, and these also have some limitation.

I don't know if you need to have your setup forcibly based on Windows Installer engine. If this is not your case, I may suggest you to consider the possibility of building up your installer on the Native Engine instead.
https://www.installaware.com/mh5/desktop/nativeengine.htm

Native Engine is designed to provide a faster, non-transactional alternative to the Windows Installer engine. You cannot create binary differential patches for setups built with the native engine. However, Native Engine is not bound to the strict Windows Installer rules, and it gives you much more flexibility and freedom with the setup logic...including update deploying.