Crashes and Memory Usage | IFS Community

Crashes and Memory Usage

  • 13 May 2022
  • 1 reply

We are on Apps10 UPD9 Enterprise Explorer, .NET Runtime 5.0.14. .NET Framework 4.8, Windows 10 Pro, build 19044. We are experiencing a high number of app crashes, specifically when users are navigating or utilizing Service-related areas. We tried multiple trouble-shooting steps initially, such as reducing cached pages to 5. We recently increased one of our units to 32GB of RAM. We are in the process of testing this now. Our standard is 8GB and generally works perfectly fine for all of our apps, including Apps8, which we were on previously. (just a few months ago). Event viewer often shows Event ID 1000 and Event ID 1026.

Has anyone else experienced this issue? Any ideas on a potential fix, aside from the RAM increase or moving to a more recent UPD? Our systems meet the hardware/software/OS requirements set forth by IFS.



Best answer by Ben Monroe 15 May 2022, 00:00

View original

1 reply

Userlevel 4
Badge +8



IEE is a 32-bit application, which means that it is only possible to address 2^32 bits of memory, which is 4 GB. Normally the OS will reserve half of this leaving only 2 GB. However, IEE (in APPS 10) has enabled /LARGEADDRESSAWARE which allows the full 4 GB address space to be available when running on a 64-bit OS. However, even if the environment has 8, 16, 32 GB, or even more memory, IEE will never be able to use it. However, that memory is not entirely wasted: extra memory will be usable to other applications (OS tasks, Excel, Chrome etc) running concurrently on the machine.

IEE was made a 32-bit application for two reasons: 1) when it first came out, 32-bit OSes were still commonly used, and 2) various integations (often requiring IE and COM) become difficult to support at 64-bit. The long-term solution is to migrate from IEE to browser-based Aurena. Aurena runs in Chrome which may run with a 64-bit address space.

Things have changed in the years since then. 32-bit OSes are rarer with most businesses now running 64-bit Windows. Also, users are now running more data-intensive tasks that require more memory than was possible just a few years earlier.

If you unable to migrate to Aurena, probably a non-technical solution is needed. Ideas would include analyzing your regular usage to minimize on memory usage. Perhaps a consultant could help with that. At worst case, while inconvenient, periodic restarts of IEE throughout the day would be one easy method to clear everything.