insufficient memory error

[Vilmos Nonn]

Hi

With the new version 6.1.2 with the same setup file on some computers the following error occurs with verysilent parameter, with interactive installation the error does not come:

Error reading FPreparingMemo.Lines.Strings: System Error.  Code: 8.

The error does not come on all computers, but on the same computer always comes.

Does anyone have any suggestions on how to avoid this?

Thanks

[Eivind Bakkestuen]

Try disabling anti virus/malware checkers to test if that helps?

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/innosetup/6d362e61-6424-47b2-bb4b-31275802cdfan%40googlegroups.com.

[Vilmos Nonn]

I can't try this so easily, this has occurred with some customers.
But I strongly doubt that this is the solution, because when the setup is run normally, i.e. not Silent, the error does not come (thank God...)

[Codec Guide]

I have also seen this error occur.

Some observations:
- It already happened in older versions of InnoSetup.
- It happens very rarely.
- It can happen on the location mentioned above, but also later in the code, included during initialization of custom pages.
- Most often error code 8. Sometimes error 1400, or "call to OS function failed".
- It usually happens on systems with a long uptime.

This may be of use for Martijn/Jordan:
https://stackoverflow.com/questions/507853/system-error-code-8-not-enough-storage-is-available-to-process-this-command

[Vilmos Nonn]

Thanks, I have already found the same entry, and immediately checked the heap size.
SharedSection=1024,20480,768, that should be enough
My guess is the ATOM table, but unfortunately that is not so easy to influence.
Possibly can advise the customer to restart his server sometimes.
But is there a safe solution?
I have temporarily made a downgrade to Inno to 5.6.1, with this version I have never had this error.