/
Best Practices & Memory crash Prevention

Best Practices & Memory crash Prevention

Owned by Regaah R
Last updated: Mar 03, 2022
2 min read

Summary

  • Iguana service runs out of memory causing a crash

  • Crash dumps may or may not be produced

  • ServiceErrorLog may or may not contain details regarding the crash

  • Sometimes in ServiceErrorLog:

    [ERROR] Traceback (innermost last): Error -2147483392: Unhandled exception

  • Sometimes in Windows event log:

    Faulting application name: iguana.exe, version: 6.1.4.0, time stamp: 0x5fc81029 Faulting module name: iguana.exe, version: 6.1.4.0, time stamp: 0x5fc81029 Exception code: 0xc0000005

  • Sometimes on a linux machine: Out of memory kill signal

    Out of memory: kill process 1342 (iguana) score 973 or sacrifice child

Troubleshooting and Possible Solutions

Case 1: Server ran out of Memory

  • Iguana continuously crashes and creates 0 byte crashdump files

  • In most cases, either the server ran out of memory or there’s not enough RAM

  • When crashdumps are created, they are usually large files that can be multiple gigabytes. Iguana creates 0 byte crashdumps when it tries creating the dump files, but runs out of memory.

  • Processing large files may increase memory

  • Ensure the server that Iguana is running on meets the recommended system requirements or increase RAM on the server

  • Setup some sort of a monitoring to view memory usage on the server and notify users if memory is gradually increasing

  • For Linux machine check: Out of Memory Kill Signal The amount of memory a process uses is based on an OOM score from 0 to 1000. TIP: See how much the current score of a process is by running

    cat /proc/<pid>/oom_score

Case 2: Other applications on the server consuming Memory

  • Iguana continuously crashes

  • Customers may assume a memory leak within Iguana, that was eating up a huge chunk of memory, when in fact there were other system processes that were the cause for it.

  • For example, in one case there was a monitoring program outside of Iguana that uses the Log API. It queried all the logs on an Iguana server, which cause memory to not get released properly.

  • Setup some sort of a monitoring to view memory usage on the server and individual applications and notify users if memory is gradually increasing

Case 3: Memory Corruption

  • Unexpected crash

  • Oftentimes hard to find the root cause of it

  • Check Windows event log or any linux logs
    for e.g Windows event log may throw Exception code: 0xc0000005

  • It may be related to Access violation error. This can occur with any Windows application due to registry issue, faulty RAM, corrupt drivers, virus infection, or incorrect security update, etc.

 

Related content